Oh, I should add this of course.... I think that is what is happening, it is the only explanation I have for the moment.
On 9/28/07, Andrew Jensen <[EMAIL PROTECTED]> wrote: > It creates one using an identity, which of course doesn't require it > to actually declare a PK as it is implied. But then when it hits the > column that is the Real PK it does add the declaration for that. When > it hands this to the engine, of course the engine barfs. > > Also it is not the same if you use ODBC to handle the MDB file, vs MS > Access that uses ADO. Both driver choices end up with an error, but > one gave me enough of a clue to figure out was happening ( odbc ) and > the other did not. > > There is an issue here, but I am not quite sure how to write it up > just yet, or if there might not be more then one. I'll let this list > know the details, and then see what really needs to be put into > IssueTraker. > > On 9/28/07, Ocke Janssen <[EMAIL PROTECTED]> wrote: > > Hi Andrew, > > > > Andrew Jensen schrieb: > > > 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. > > > > > Does Base try to create two primary keys or only one with two columns? > > If first please submit an issue :-) > > > > Best regards, > > > > Ocke > > > That is where the fun begins...more later. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Ocke Janssen Tel: +49 40 23646 661, x66661 > > Dipl. Inf(FH) Fax: +49 40 23646 550 > > Sun Microsystems Inc. > > Nagelsweg 55 mailto:[EMAIL PROTECTED] > > D-20097 Hamburg http://www.sun.com/staroffice > > > > Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, > > D-85551 Kirchheim-Heimstetten > > Amtsgericht Muenchen: HRB 161028 > > Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer > > Vorsitzender des Aufsichtsrates: Martin Haering > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
