deployment issue

Hello all,

I was wondering if anybody had this type of issue, and how they
handled it.

I have a DB that sits on a server that lets everyone do the "open
remote" bit to access it. We want to start using the DB for field
work, but the problem is is that the worker won't have internet access
in the field.

What is the best strategy in terms of letting him use the Db in the
field and be able to "sync" back up with the database on the server
without running into issues of primary key numbers that are set on
creation?

Re: deployment issue

On 2007-12-07 07:35:22 -0800, EP said:

> What is the best strategy in terms of letting him use the Db in the
> field and be able to "sync" back up with the database on the server
> without running into issues of primary key numbers that are set on
> creation?

Depends on what kind of sync you intend to use. Text files exported
from remote copies and perhaps emailed, or direct sync once the user
returns to the office?

For a pre-built, though expensive, solution, go look at Syncdek, from
World Solutions.

http://www.worldsync.com/

This takes care of uniqueness in its own way.

For roll-your-own, the remote versions (which should NOT have duplicate
names same as the hosted files) should generate keys with a prefix of
the user name or initials, or some deriviative of the machine
identification. That way if the same serial is used in more than one
remote or local installation, it's still unique in the system.

When you import, import without running the auto-enter processes, and
the keys generated in the field will remain.

This means that OTHER auto-enter processes not involved in keys, that
need to be set on import, will have to be done through script. It
becomes quite a process.

Consider providing to the remote folks some kind of wireless connection
device such as cellphone or Blackberry to connect to a web interface
for the entry of data into the central files. Anytime you can avoid the
remote/sync process, you're better off. That all depends on how complex
the processes are they are interacting with, of course, but if you can
simplify it and web-serve it, you'll be better off. What are the
costs/benefits of each approach?
--
Lynn Allen
--
www.semiotics.com
Member Filemaker Business Alliance
Long Beach, CA