A few comments:
First, you shouldn't need to browse to the backend; you can extract its
location from the Connect property of the TableDef for any linked table.
Second, most backends rapidly exceed the 1.44 MB you can store on a floppy.
Third, it's generally considered unwise to copy an MDB file while there's an
open connection to it.
At the very least, you should make sure that all bound forms in your front
end are closed. (Put your button on an unbound form - e.g. a switchboard or
main menu.)
Since you have a split application, I'm assuming that there may be other
users using the backend at the same time. It would be best to check for
this condition and not allow copying in that case.
Fourth, the FileCopy command is all you'd need to copy the file to a new
location on a hard drive or floppy drive. Under WindowsXP, I would expect
it to move the files to the D drive for you, but not to actually burn the
CD. If you come up with some API calls to actually do the burning, please
post back. I'd like to know those myself!
HTH
- Turtle
"DD" <da**********@bigpond.com.au> wrote in message
news:14**************************@posting.google.c om...
Hi
I have a split database, that is packaged and used in a runtime
enviroment.
I want to make it easier for the user, a button on the frontend
"Export Backend"
They can click on the button then search for the backend and then save
the backend to a CD or Floppy.
Can anyone assist,as i have looked at the OpenSave dialog but i must
be missing something
Regards
DD
