Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

This in effect works if the database was originally created as a split database one effectively then one gets the screen Ratslinger pictures above and the autovalue is properly created.

However if a database was originally created as an embedded database and it is opened as a split database one gets this screen when creating a new table in that database:

Test

Then when one attempts to enter data and save the first record one gets this screen (note that autovalue is not in the ID field):

Test of data entry

However running the sql commands proposed by Ratslinger above does remedy the situation, except for the problem of the 0's appearing noted already as bug.

This in effect works if If the database was originally created as a split database one effectively then one gets the screen Ratslinger pictures above in the other answer to this question and the autovalue is properly created.

However if a database was originally created as an embedded database and it is opened as a split database one gets this screen when creating a new table in that database:

Test

Then when one attempts to enter data and save the first record one gets this screen (note that autovalue is not in the ID field):

Test of data entry

However running the sql commands proposed by Ratslinger above does remedy the situation, except for the problem of the 0's appearing noted already as bug.

If the database was originally created as a split database one effectively then one gets the screen Ratslinger pictures in the other answer to this question and the autovalue is properly created.

However if a database was originally created as an embedded database and it is opened as a split database one gets this screen when creating a new table in that database:

Test

Then when one attempts to enter data and save the first record one gets this screen (note that autovalue is not in the ID field):

Test of data entry

However running the sql commands proposed by Ratslinger above in the other answer to this question does remedy the situation, except for the problem of the 0's appearing noted already as bug.

If the database was originally created as a split database one effectively then one gets the screen Ratslinger pictures in the other answer to this question and the autovalue is properly created.

However if a database was originally created as an embedded database and it is opened as a split database one gets this screen when creating a new table in that database:

Test

Then when one attempts to enter data and save the first record one gets this screen (note that autovalue is not in the ID field):

Test of data entry

However running the sql commands proposed by Ratslinger in the other answer to this question question, does remedy the situation, except for the problem of the 0's appearing noted already as bug.