Importing data

  • Thread starter Thread starter Joe
  • Start date Start date
J

Joe

We are considering using laptops in the field and would
like to import the data from the laptops to our database
on our server. The database on the server has the same
tables and forms as on the laptops and our secretary will
be inpuiting information into the database while we are in
the field. How do we prevent from loosing informatio or
creating many useless tables?
 
Joe said:
We are considering using laptops in the field and would
like to import the data from the laptops to our database
on our server. The database on the server has the same
tables and forms as on the laptops and our secretary will
be inpuiting information into the database while we are in
the field. How do we prevent from loosing informatio or
creating many useless tables?

You could have a form in the program on the laptop for the
user
to execute a procedure to update the server database. The
user
could click a button. Behind the button, the code would open
an "Open Dialog Box" and allow the user to find the correct
database
on the server and select it. This would give your laptop
program the
path and database name. You can then create the workspace and
link
in the table(s) to the laptop db and have the procedure update
the server
database using an append queries, or dao, or ado add and
update logic.
At the end of the procedure your would close and delete the
links in the
laptop program. You will also need to make the server database
a shared db
if it's not already.

Ron
 
Back
Top