OK - this is really just a place holder for a new discussion about copy table / import functions.
I'll come back and start to it off in just a little bit, after I finish helping Swarup do what he needs to do. I'll start it off here by just saying this - MS Access allows you to create auto incrementing integer fields that are not used as part of any key. So, does HSQLdb, but in MSA you just declare them as auto increment and don't assign them to the key. In HSQLdb you have to create an sequence and then create an integer field, and set the default to use the sequence you created. HSQLdb supports this short hand trick of declaring a type IDENTITY if you also want to use it as a PK. The Base copy table wizard doesn't really seem to understand that a COUNTER field in MSA might not be part of the key, and so creates an IDENTITY. Problem is, the table uses a varchar field as the PK, and then Base attempts to create a table with 2 PK's...well, that doesn't work of course. That is where the fun begins...more later. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
