![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
This is my problem: I have a database installed on SQL Server. I wish to be able to export this database to a Access .mdb database. My problem is that autonumber fields are not easily replicated. Example: A conference can have a number of participants tblConference {id, confname} 1----n tblConferenceParticipant{id, ConferenceID, ParticipantID} n---1 tblParticipant{id, ParticipantName} Data example: 1, conf1 1, 1, 5 5, Paul 2, conf2 2, 1, 7 7, Kim 3, 2, 1 11, John My problem is not getting the data transferred to the access database. My problem is that I need the database to be functional, eg. if a user decides to use an Access copy of the database, it will produce new ids as new participants are added etc. The "gaps" (eg between 5 & 7 in tblParticipant) in the original SQL Server database need to be copied as well. If they aren't, even if the autonumber function works perfectly, the above will break: Since the ids in tblParticipant would be 1,2 and 3 the relations in tblConferenceParticipant would be "broken". I have tried exporting the data to Access first, but I cannot bring Access to make a field autonumber after puttning data into the table. The fallback solution right now is to create a VBA script to run from Access, importing the relevant tables from SQL Server. Ideas would be greatly appreciated. Sincerely Poul Ingwersen |
![]() |
| Thread Tools | |
| Display Modes | |
| |