M
Max Moor
Hi All,
I'm not ready to implement replication, but I need to be able to copy
my backend so it can be borrowed off-site. I thought I would just add some
code to a menu item allowing the backend to be copied and renamed. Also,
I'll set a flag warning users that the database has been "checked out," so
they don't use it until the backend is returned.
Can anyone tell me what issues I may be in for, in trying this?
Obviously, I stand to lose any data entered between checkout and checkin
time on-site. Are there any issues with copying the backend to another
place while the fronttend is running (even assuming all forms and reports
are closed)?
Finally, when the backend is returned, I need to rename the existing
one, copy in the returning one, naming it back to the standard name, and
then delete the old copy. Can I rename a backend with the frontend
running?
I'd appreciate any advice or alternative suggestions, short of
implementing replication.
Thanks, Max
I'm not ready to implement replication, but I need to be able to copy
my backend so it can be borrowed off-site. I thought I would just add some
code to a menu item allowing the backend to be copied and renamed. Also,
I'll set a flag warning users that the database has been "checked out," so
they don't use it until the backend is returned.
Can anyone tell me what issues I may be in for, in trying this?
Obviously, I stand to lose any data entered between checkout and checkin
time on-site. Are there any issues with copying the backend to another
place while the fronttend is running (even assuming all forms and reports
are closed)?
Finally, when the backend is returned, I need to rename the existing
one, copy in the returning one, naming it back to the standard name, and
then delete the old copy. Can I rename a backend with the frontend
running?
I'd appreciate any advice or alternative suggestions, short of
implementing replication.
Thanks, Max