Multiples of the Same Database

[joseppic]

Hi,

I have created a Database consisting of a number of table and relationship fp5 files. I wish to provide a version of this database for a number of projects my people are working on.

Is it possible for multiple versions of the db files to keep their original filenames when served as long as each group of files is in its own sub-directory?

e.g.

fmserverroot/project1/work.fp5

fmserverroot/project2/work.fp5

fmserverroot/project3/work.fp5

This would stop the game of renaming every fp5 file each time a new project is started.

Any ideas/advice greatly received.

take care,

J.

[Ugo DI LUCA]

Hi,

I've read some comments about bad "interractions" of files which same name even in its own directory. I've personaly experienced strange behaviours on a single computer (from my back-up files) and I don't think the server would be more secure.

Is there any reason why you couldn't keep all the Projects in a single Project db, using a relationship ProjectToProject to lead the user to its specific work records and layouts.

[joseppic]

Good point Ugo, I'll speak with those in authority and see what they think, otherwise looks like I'll be renamins all my files and re-pointing all my scripts.

Is there a quick way to do this??

take care,

J.

[Ugo DI LUCA]

Joseppic,

This post have been posted a few minutes ago and could "reasonably" offer a better explanation of my previous answer + security procedure.

Cobalt as usual... .

For the tool, I think you should use FM Developper as it come with a Developper tool. But I'm just guessing from what I've heard as I don't use it (for the moment).

[Anatoli]

Developer has nice tool for renaming and relinking the solution.

Note: Developer will not take care of pointing external scripts to correct files in all cases. Only files running from the same computer (e.g. server) will have the script links changed.

In solution, which is using files from different locations the scripts linking will sometimes not work. Like 20 files running from server and 5 from local client and calling each other scripts.

[LiveOak]

We support a large client with 5 FM Servers running project specific sets of the same files. I strongly urge you to give each project set unique names. If you don't, there is no way to keep cross connections and corruption from happening short of having only a single project set open at one time using FM Server.

FM Developer Tool is the answer to the renaming problem. I would also suggest using FM Server to host the files.

-bd

[Anatoli]

Amen!