Thanks, when this version is available for download so I can try it out. >> I'm not sure about that. Is the problem just with auto-increment >> primary key, or is it with all kinds of primary keys? Meaning, does >> this work: create table(id int primary key, name varchar(255))? I >> think it's not yet fixed (unfortunately I don't have MS Access >> currently so I can't test it).
The problem is with primary key and unique key, the auto-increment is not a problem. >>> If I make the field INT AUTO_INCREMENT, there is no problem linking to it. Thanks On Jul 4, 9:42 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > I have fixed some problems now (in the trunk). > > > DBNAME;CIPHER=AES > > That should work now. > > >> - Unable to link to a table that has a field with primary key or > >> unique key > > I'm not sure about that. Is the problem just with auto-increment > primary key, or is it with all kinds of primary keys? Meaning, does > this work: create table(id int primary key, name varchar(255))? I > think it's not yet fixed (unfortunately I don't have MS Access > currently so I can't test it). > > > when a table has _ (underscore) in the name > > That should be fixed now. > > Regards, > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
