H All,

FM8.5 mac OS X.4.8

I have 2 copies of a Private Practice Accounts solution set, now on a
server, using different filenames, in different directories. Structure
is data separation model. Names (with .fp7). Using FileMaker Network
Sharing.

directory PracticeA
A_User
B_Data
C_PracMan

directory PracticeB
A_UserPB
B_DataPB
C_PracManPB


Modifications and development is done in the Practice A set (on my
laptop, i.e. not the server) , and any A_Data file changes, duplicated
(manually hard coded) in PracticeB B_data. The majority of dev happens
in A_User. I then copy (system duplicate) or clone A_user, rename it
drop it in directory PracticeB, overwriting the existing version (with
FM quit), launch, redefine the File References; only 2, to B_data, and
to C_PracMan.

The result is far from perfect. Scripts fail and fields drop out from
layouts.

Yesterday I cloned A_data, with FM quit, removed the original B_data
from its directory, renamed the clone B_Data and moved it into the B
directory. I also cloned the A_user, and replaced the B_User with the
renamed clone. So both user and data in directory B, are copies of those
in A. I then imported all (23) tables form the original to the renamed
clone. This cured a number of issues, but user scripts still have field
drops, and layouts lose field definitions.

This is a chronic problem, and I need an effective strategy for
development in one solution set, then updating the second solution set
with the new User version. Normally this is a no brainer, and a simple
drop/replace in file sets with the same names. Having to rename and
repoint is causing the problems.

This has been a problem even when the two solutions (Practice A,
Practice B) resided on different computers. My requirement is to just
replace the B_User (and C_PracMan) with their renamed updated A set
counterparts (user interface files), leaving the data file untouched.
Just like rolling out any version update using data separation. Rename
and re-point is unavoidable. The confounding issue here, is having to
have some file name differentiation between the two solutions.

Any suggestions?

regards

Chris Brown
University of Adelaide