Importing vfp database a number fo tables fail to import

[avianmanagement]

I used drag and drop to import a vfp database into Lianja

For a number of tables is says it failed to import table

Importing table 'da10application' from 'c:\visualaims\data\da10application.dbf' - failed to import table

Where can I look to see why it failed as there is no error message in the log from the console

[avianmanagement]

I also get

Importing table 'd7column' from 'c:\visualaims\data\d7column.dbf' - failed to import table

So it does not look like it's a case of a long table name

At the end of the import run I get

Import of Visual FoxPRO database 'aim' completed successfully

Whilst the databases may have been imported all it's tables were not. Would be more user friendly if the message at the end told you some had failed.

If I alter the code on the import prg I assume it will get overwritten on a Lianja update?

[barrymavin]

Hi David,

Long table name? Do you mean long column name?

VFP stores long column names in the dbc not the table making them incapable of being moved out of the dbc. This is most likely why your indexes failed to convert also.

Yes. Any updates will overwrite your changes to files included in the lianja distribution.

[avianmanagement]

Hi Barry,

No I did mean long table name as the first example I gave had a long name, da10application as opposed to the second which was shorter d7column.

I'll take a look at the length of the column names.

Is there any type of error report created by the import process that I can see exactly why the import failed on certain tables?

David



Thank you

[avianmanagement]

Hi Barry,

Trying to see in the Lianja help file the max length, but can't see to find a reference to it

It has imported table column names that ar 17 long, maybe others in there that are longer. I understand that max length in vfp9 if it is not stored the database is 10 characters.

Therefore is this a column name length issue or an index issue because of a long name do you think ?

I'll see if I can step through the import prg and see what is happening. I know I had index issues in the past trying to import, but not names for columns per say

David

[barrymavin]

Hi David,

The table names are not an issue.

[barrymavin]

Max filename length is 512.

Windows imposes a maximum path length of 255 characters.

[barrymavin]

In the console.

use path\to\table
list structure

You can open native VFP tables you just can't update the indexes.

[avianmanagement]

Sorry Barry bad wording on may part in the post.

What I was looking for in the help file was the max name length for a column.

Since it is importing long column names do you think the issue is with a ling name being used on an index?

I'll step through the code and see where it is failing.

[barrymavin]

32 is max field length.