how to I transfer new data from my laptop to my desktop in access

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have access 2000 and I am using the "service call" template on my laptop
and desktop. What is the best method for updating my desktop from my laptop?

Thanks,
 
Somebody (Please!!) stop me if I'm on the wrong trail but isn't that what
replication is for?

I don't know anything about replication.

Mike
 
Mike Revis said:
Somebody (Please!!) stop me if I'm on the wrong trail but isn't that what
replication is for?

I don't know anything about replication.

Mike
Click to expand...

It very much depends on what the OP is trying to accomplish. It might be a
simple matter of copying the .mdb file from the laptop to the desktop.
 
So the question to the OP is this:
Will changes be made on both computers, so that you need to merge the
two copies? (In this case, replication can help.)
Or will changes only happen on one computer at a time? (e.g., you take
your laptop out into the field, but nobody is working on the desktop while
you're gone.)
In that case, just copying the mdb back and forth could be all you need.
 
I believe that's true.
You can copy the .mdb to the laptop, take it home, work on it and then copy
it back to the desktop.
As you say, it depends on the goal.

Mike
 
See Replication in Access Help,
Though you could simply copy the db back and forth, you leave yourself open
to disaster doing this.
 
I use the "service call" template in the field on my laptop [or at least plan
to] and want to update my desktop with the changes. Their should be no one
else working on the desktop [small company]. I thought there should be a way
to do that without manually copying files and replacing those on my other
computer, something like a backup file that would insert new data into either
computer.

I will look up the "replicate" as suggested. [I did look in help first, I
also use a Shelly Cashman series Office 2000 manual but it seemed to not
address this issue]

Thanks
 
I'm curious about this comment -
I've heard of a lot more disasters using replication than simple file
copies.
For an even higher degree of safety, rename the old database before
copying a new one in, so the old one can be retrieved.
And for convenience, automate the whole process with a batch file.
 
I should have expanded;
Allways have a copy of origonal db (lasted updated db) so you are working on
copies, if it goes wrong - numerous reasons - you are able to recover the
origonal
 
Thanks for all the responses,

I will follow up on all the suggestions.
This is my first time using this forum and I am not sure I am using the
"rate a post" correctly since it seems to only give one option. The forum is
great but kind of overwhelming almost for a dial up ISP.
 
Back
Top