Jump to content

topic

Newbies
  • Posts

    2
  • Joined

  • Last visited

topic's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Fenton No, there are no synchronization issues to contend with and following your comments, maybe no advantage to separating data from interface. Simple conclusion is that I have not fully understood the nature of runtime files and I need to read and experiment more before asking any more questions! Good to learn though….just need to find more time for it. Thanks for the reply, appreciate the help. Tony
  2. We are a very small business, usually one of us in and one out of the office. Our client, appointments and project information is held on an FM 8.5 database, which runs on the main office machine and in runtime versions on each of our laptops. The office machine holds current data and the idea is to update the runtime versions when we go out on the road so I’ve been looking at the easiest and quickest way to do this without having to create a new runtime version each time the main database is updated. If I understand correctly (and I may not!), rather than the single file holding all layouts, scripts, tables etc. we have at present, I should be separating this into two files, one to hold the regularly changing data and one for the layouts etc. that will only change infrequently. It’s a lot of work to separate in this way but I’m still new to FM and if I got the basic design wrong I would like to correct it before I go too far. So, is the best approach to separate as above then transfer current data to the laptops by overwriting existing data files? Hope that’s clear and I would be grateful for any guidance.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.