Synching files can be a real headache depending on how many different users may be modifying data and on which copy of the file.
If your brother is the only user of the file, you can use a simple approach. Keep the active file on the laptop at all times. When in the office, connect it to the LAN and link to it via remote access from the desktop machine or just always use it on the laptop. If he doesn't have a LAN, it's possible to use a "crossover" wired ethernet cable to directly link two computers without any hub or switch to make a "mini-LAN" for sharing the file via remote access.
If you have a user or users in the office that may be updating data while another user is updating data on the laptop, synching gets a lot more complicated.
Is it possible the laptop user will modify existing records or will they just create new records?
Is it possible that a user in the office might update a record and then the lap top user might update the same record in a different way? (Then how do you decide which copy of the record to keep when you synch?)
Once you analyze how the two copies of the same file might be used, you can devise a synch method which can be scripted, but which could become very complex or be fairly simple--depending on how you need it to work for you.
Thanks for the response.
The problems you point out are certainly a concern. He will mainly be creating new records but there is a chance that he might modify an existing. My mom helps out in the office and creates/modifies the majority of the records.
That means any given record may have 6 states: Unmodified since last Synch, Modified at home office, Modified on laptop, Modified at home office and on laptop; deleted on home machine; deleted on laptop.
You can identify the state for any given record by giving it a date field that auto-enters the modification date and by also creating a synch log that adds a new record recording the date every time you synch the records.
You can import the records from the laptop in to an auxiliary table that is related by the same field as the PrimaryKey field (should be an auto-entered serial number) in the main table. You can then loop through the records of this table comparing modification dates in the two tables and that of the synch log to determine which table holds the record that should be retained. In cases where a record was deleted or modified by both users, it should display both record versions ( or the one existing version ) so that the person performing the synch can decide which copy to keep or even to merge the changes to combine the edits of both users.
Doable, but not simple. Once the synch process is complete, you can use Save a Copy as to save a copy of the newly synched file to whichever computer does not have this updated copy all as part of the same scripted process.
(Note one possible work around used to simplify this process is for the traveling user to review the records on the Home Office system and "mark" each record they might need to edit while traveling. The system would then prohibit any edits to these records on the home system until the traveling user returns and releases them.)
Thanks for all the help. Its pretty much as I thought. I was going to play around with auto enter modification and creation dates and create scripts to sort them easier for export. I'm probably going to advise him to not modify existing records on the road and if he does, to manually make the changes back at the office. For him, it might be the best advice.
Thanks again for the advice. It really is very appreciated!