andrew wrote:
Barbara Duprey wrote:
(Comments in message)
Yes, that was the specific question (let's call it Issue 1). In this
case, it would be complicated by the fact that Base did not define
the PK it generated for the original .dbf import as auto-increment.
This one has a work around.
If you drag and drop onto Base, then when the copy table wizard opens,
instead of defining the table and copying the data in, in one step you
simply create the table structure. Then when the field type INTEGER or
BIGINT is marked as the PK it is created as AUTO_INCREMENT.
After this drag and drop again, but this time only append the data to
an existing table - then the data comes in, either include the PK
value from the old table - this works as long as the values are
unique, or simply leave that field out and new keys are made. This
later approach has a down side if there are FK relationships in your
schema of course.
Yes, if I'd known how Base would handle it that's what I'd have done,
but I didn't. The redefinition process is doable, but cumbersome.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]