[FX.php List] one machine intallation

[Erik Andreas Cayré]

Den 26/04/2007 kl. 9.32 skrev Kevin Futter:

> Most of our staff members get quite disconcerted by
> layouts changing right before their eyes!

At a one-day seminar last year, I heard about a strategy to work  
around this problem:

Divide the solution such, that all raw data are in one (set of) file 
(s), and put the UI in another (set of) file(s).

Modify the UI file offline at will, and distribute it to users  
whenever practical. This has the advantage of letting different users  
have completely independent (and different) UIs to the system, and  
lets you propagate changes in more manageable steps...
In addition the UI file(s) *may* be local to the user, depending on  
the systems properties...

I'm preparing to o a complete  rewrite of my employers CRM system  
which is currently a relatively big FM6 system:
Files: 47
Scripts: 2244
Script Steps Read: 19944
Fields: 3449
Relations: 571
Layouts: 559
Fields on Layouts: 16003

I'm looking forward to being able to develop on the 'live' system,  
and so, am glad to hear most of you never had trouble doing it.
(Since FMI seemingly has no problem handling consistency of records  
manipulated by remote users, I would be surprised if they were unable  
to do the same for the integrity of structure changes, assuming of  
course that there is no problem locally on the FMS machine)

Have any of you considered the data/UI separation strategy?


---
Erik Andreas Cayré
Spangsbjerg Møllevej 169
6705 Esbjerg Ø

Privat Tel: 75150512
Mobil: 40161183

---
»Kun p....sure mennesker kan ændre verden. Innovation skabes ikke af  
'markedsanalyse', men af folk, der er afsindigt irriterede over  
tingenes tilstand «
--Tom Peters

»Hvis du ikke kan forklare det simpelt, forstår  du det ikke godt nok.«
-- Albert Einstein

»Hvis du ikke har tid til at gøre det rigtigt, hvornår vil du så have  
tid til at lave det om?«
-- John Wooden, basketball coach