Export/Import to off site static file.

[Mike J]

Hi All,

There is a need for our group to have small offline module files that can be with the user while away from our network.

So two files: Module File and Parent File

I have a subset of tables in the module file that pertains to the off site requirements. When off sight, the user can enter data, but can't created new records.

When they return, they need to update the parent file by importing from the module file to the parent file.

If the parent file is served on another computer or server, how would I initiate the script for export/import?

Export: User is in the parent file, selects the appropriate records for export and initiates it from there.

-How would I locate the parent file in a script step?

Import: User is in the module file, initiates a button with a script that begins by looking for the parent file.

-How would I locate the parent file in a script step?

I'm good on all subsequent importing, match fields etc. It's the location part that I'm struggling with. What if the parent file moves to another server. How do I soft code (i guess this is a term)?

Thanks for any assistance or links to other relevant topics that addresses this question.

Mike

[Ocean West]

Mike, this sort of solution would require a UID ( universal ID ) - you say they DON'T create record but i would assume that your tables are not 'flat' and have children records related to the parent record so you are creating records in other tables however only editing parent records.

I would strongly recommend SyncDek by WorldSync http://www.worldsync.com/syncdek/index.html which is built for this exact scenario that you describe.

Better yet the users don't necessarily have to be in the office, to sync your data as the only requirement would be a internet connection.

Other methods for this would require you to flag which records on the server in the office are being checked out for the remote user - thus locking them from editing while out in the field. As conflict resolution is not something trivial.

Hope this helps

Stephen

[Mike J]

Hi Stephen,

That is correct, this is not a flat solution. They would create only one record in a related table. I have restricted editing of the parent because most of the data on the parent is hardly every edited or changed on a monthly basis.

The unfortunate problem is the internet connection. Our IT group does not offer 24/7 service. In the event our connection goes down (onsite server issues or ISP lines), the only solution I know is for IT to file dump twice daily to a static IP that I can access. I am not allowed, for security reasons, to access the server rooms.

This file dump will allow me to access data from this computer and and provide static data to our users so that they can take it to their work site.

I'll look at the link you mentioned. I don't think the flagging records is an option in this case since everyone's static file will update the parent I control before it goes back online.

Any other reccomendations would be helpful if others have dealt with a similar problem.

Thanks

Mike

Edited April 21, 2009 by Guest