Don't copy the database anywhere. Just rename it (name, type and creator), create the temporary one, invoke HotSync, delete the temporary one, then restore the name of the original database.
You'll probably want to play nice and have something that runs at reset that checks to see if a crash left the original database in a renamed state and clean up. On 9/18/07, Christopher Stamper <[EMAIL PROTECTED]> wrote: > Feature memory? Put a .pdb in feature memory? Are you serious? > > I don't plan to 'disassemble' the pdb and copy records, I am not that > advanced a programmer... > > On 9/18/07, Michal Seliga <[EMAIL PROTECTED]> wrote: > > Christopher Stamper wrote: > > > Good idea! I could backup file before I call sync, then restore it > after! > > > > > > Oh, but then they'd need an expansion card. > > > > > > Thanks so much!! > > > > what for? you can backup data to feature memory, or create new database > and copy > > it there record after record..its not only one api call, but expansion > card is > > definitely not needed. and for these few records it will be quick anyway > > > > > > -- > > For information on using the ACCESS Developer Forums, or to unsubscribe, > please see http://www.access-company.com/developers/forums/ > > > > > > -- > Christopher Stamper > [EMAIL PROTECTED] -- For information on using the ACCESS > Developer Forums, or to unsubscribe, please see > http://www.access-company.com/developers/forums/ > -- [Jeff Loucks] -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
