Error when importing VFP database

**barrymavin** · 2012-11-27, 10:08

Ok thanks i will take a look.

**barrymavin** · 2012-11-27, 19:45

I have been looking at the issue you reported what you did not say is that this database contains a lot of views. That is causing an issue as some of the views reference tables that have not yet been imported.

The handling of views that have dependent tables which is causing an issue. Difficult to handle as we would need to parse the SQL query in the importer.

Also worth mentioning is that I note that some of he views contain parameter markers that reference external memory variables. Nothing wrong with doing that except it makes it impossible for Lianja to let you visually design anything with those views without you having meddled with setting up memory variables beforehand. That is going to be problematic using these views client server with Lianja SQL Server and also Lianja Cloud Server.

So as things are at the moment you can't import .dbc databases which contain views.

There is an some strange behavior in the database imported as you mentioned and i am looking into it now.

**gtgeek88** · 2012-11-27, 20:09

Ok, thanks for letting me know. It's not that I need it imported exactly as is. I may not need views in a Lianja app, right? The problem I encountered was on the ROLL and ROLL_DET tables and on the STYLE and STYLE_DET tables, as explained in the initial posting. The views are less important to me (at least right now).

**barrymavin** · 2012-11-27, 20:17

This has now been fixed in RC1. See attached screenshot.

Thanks for bringing this to my attention.

Name: import_rc.jpg
Views: 157
Size: 28.7 KB

**gtgeek88** · 2012-11-27, 20:32

Did it have anything to do with the table names? Or was it just a coincidence that the tables it happened on both started with the same characters?

**barrymavin** · 2012-11-27, 20:53

No. It was a bug in the importer. Classic VFP bug to do with EXACT string matching. Anyway, it's fixed now.

**gtgeek88** · 2012-11-27, 21:22

Well, ok, but ROLL_DET and ROLL match on the first 4 characters and with SET EXACT OFF, ? "ROLL_DET" = "ROLL" returns .T.

Anyway, I'm glad it's fixed. Thanks.

**barrymavin** · 2012-11-27, 21:41

Yes I know. It was something internal that had the logic the wrong way round.

**avianmanagement** · 2012-11-28, 01:54

Originally Posted by barrymavin

I have been looking at the issue you reported what you did not say is that this database contains a lot of views. That is causing an issue as some of the views reference tables that have not yet been imported.

The handling of views that have dependent tables which is causing an issue. Difficult to handle as we would need to parse the SQL query in the importer.

Also worth mentioning is that I note that some of he views contain parameter markers that reference external memory variables. Nothing wrong with doing that except it makes it impossible for Lianja to let you visually design anything with those views without you having meddled with setting up memory variables beforehand. That is going to be problematic using these views client server with Lianja SQL Server and also Lianja Cloud Server.

So as things are at the moment you can't import .dbc databases which contain views.

There is an some strange behavior in the database imported as you mentioned and i am looking into it now.

If views are in a separate DBC and one imported the table DBC 1st could one then import the view DBC ?

In Lianja how would one hand the situation where views need to have parameter markers that reference external memory variables, such as tableName.dDate > ( ? ldDate )