Exporting to PostGreSQL with AutoIncrement field

View: New views
1 Messages — Rating Filter:   Alert me  

Exporting to PostGreSQL with AutoIncrement field

by Arthur Baldwin-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hello again,

I found the answer already to the combobox question.  Moving on again.  I was able to add the .mdb driver to the list of database types that Knoda understands.  Then I opened up a .mdb file and tried to export it into PostGreSQL.  Unfortunately, while the first field in every Access table is "AutoIncrement", the finished field in PostGreSQL is of type "bigint" and not "bigserial" or even "serial" as desired.  OK, so I figured that I could modify the tables after exporting, but then the field order is all wrong.  So then I thought maybe there's a way to modify the table in Access before exporting and still recover the relationships between tables...but after some thought I gave up on that idea.  So really the solution is to correctly export from Access to PostGreSQL or MySQL with the correct datatype in the resultant export.  Any idea when this might become a reality?

Arthur


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Hk-classes-discuss mailing list
Hk-classes-discuss@...
https://lists.sourceforge.net/lists/listinfo/hk-classes-discuss