vpn to FMserver

[Ben Ball]

Not sure if I should make another topic related to another post I recently made? but it is kind of a different topic... related to.

 

This is related to Filemaker 11.

 

I have a VPN (virtual private network) which connects me to an FMserver which is located on a virtual server in a different location.

 

I have a database on the fmserver which is the master database.

 

I have a database on my PC that has a table (design) that connects to a sister table (design) on the fmserver.

 

I have an identical table/fields/layout in both databases.....

 

I find it absolutely amazing/astonishing that with the database on my PC it will show me all the records from the file on the fmserver.

 

If I create, change or delete a record on my PC, it will update the file on the fmserver. Visa versa.

 

If I disable my VPN connection.... The file on my PC.. I will obviously have no records and all the fields will have no identity.

 

If I re-connect... all the records come back...

 

Now.. what are dangers of this set up? It has some great advantages to me.... But I am obviously worried about it.... If the VPN connection breaks for some reason... whilst I am working on records that are linked to FM server.

 

Hope this makes sense? Any advise on this set up is appreciated.

 

I am not even sure how its possible for the records to be there on a completely independant database.... I can see how they would appear through a portal.... but its actually showing records on the database on my PC??

 

 

 

 

 

 

[bcooney]

"I have an identical table/fields/layout in both databases....."

 

I really find that hard to believe. I think that what you have going is a Separation Model. You have a local file for the interface, but all the data is on a served file.

 

Your VPN is not connecting you to the FMS. The VPN connects you to the LAN, and the FM file can now see the served file that is on that LAN.

 

These two files are not completely independent. The local file has the served file as an External Data Source.

 

"Now.. what are dangers of this set up? It has some great advantages to me.... But I am obviously worried about it.... If the VPN connection breaks for some reason... whilst I am working on records that are linked to FM server."

 

Yes, the VPN connection breaks you might have an unsubmitted record edit. If you are running a script and the connection drops, then you might have a half-completed transaction. Hopefully, all transactions are designed to handle a connection drop.

 

Do you know who is the Admin of this system? If you do, these are questions for her/him.

[Ben Ball]

That's really the question.. What script steps can I enable that will handle a connection drop?. I really was'nt expecting to get records in my system by taking a clone of one database, putting it on a different pc and then linking it to itself.... But no.. They are not completely. Independent.... I am linking the tables via fmnet:/ipadresss/filename

[bcooney]

Transactional scripting. Read Todd Geist's blog.

[LaRetta]

What script steps can I enable that will handle a connection drop?

If you are data-entering directly into fields then there are no scripts to break; if typing directly into fields then you will not have an unsubmitted record edit. I doubt that all developers set every WAN or VPN solution up as transactional. It fits specific need when parent/child results are entwined. Even if you use transactional, a script still writes and could still potentially fail even on LAN or desktop.

I would not be able to give blanket suggestion, sorry, only that 1) your scripts should error trap and branch accordingly, 2) all records should contain auto-enter creation and modification timestamps and auto-enter Account Name so you can find a break if it does happen and 3) use scripts as little as possible and let the system mostly run itself. This is true in general and includes script triggers which are over-used for critical tasks.

If you are entering someone's payroll from an iPad (where parent/child combine to generate totals) then that is a different issue from just entering data or creating a new record. As always true, every situation should be evaluated independently and the "safest + lowest footprint - complexity" is the best formula.