Schema development on Server

[bluearrow]

Hi,

I am not sure this is the correct forum for this question, but here it goes:

What are the cons of schema developing using a client machine opening a hosted file in FMServer? Please take into account that I am always referring to a wired LAN, never a WAN, not a wireless LAN.

I have read some negative advice, but not the reasons for it.

I can see some big advantages:

If I develop using the hosted file, then all global fields, calculations, variables, etc would behave exactly as they finally would. If, on the contrary, I develop with a local copy, this might not be the case and I might not be aware of an issue until I finish the development.

Another good point for working with a server hosted file is the stability of the machine, compared to a local machine (for instance, if there is an electricity supply problem). Server machines do generally have RAID disks, standard backup routines, etc.

So, what are the negative points, if any? what should I take in consideration if I decide to go the server route? or should I never go this route at all?

Thanks

[Genx]

Well.. the only real concern is if the connection breaks, but given that you have a wired connection and provided you have backup routines, and the file isn't actually live (though it's not a mandatory requirement, it will make it safer), there shouldn't be any huge issues..

The main advantage though is multiple developers working on the file at any given time (as opposed to behaviour). Globals and variables are both session specific and it's just a standard fact... if they confuse you, read up on them or do a search on the forums, their behaviour is discussed in depth in various threads.

[Ender]

Since modules are often tied together in various ways, I usually develop new modules and major revisions off-line (on my own computer). This way there's no problems waiting for users with open records or with accidentally changing something that gets active users into incomplete or old processes.

For me, it's also easier to make a quick archive at various stages of development and give it a useful name. With Server, the backups would be replacing themselves at regular intervals, and you might not remember to make an archive for a particular development stage.

[Genx]

I use both methods, and can't say i prefer any one..

When developing offline i make myself backup scripts to zip my backups and add to a version log.

When on server i run 24 backups (1 per hour) and archive the last backup of each day using a trigger vbscript. Then once every couple of months (if the project goes for that long) i move the backups to a disk. I think Wim has a good a sample for this on his site (think).

[bluearrow]

Thank you both.

Your replies clarify my main concerns. I think I will opt to develop using a server hosted file, making backups using a batch file to rename those backups regularly (to avoid FMServer overwriting its own backups).

I was more confident developing locally with version 6 downward than with version 7 upwards. In my case, I use an external server authentication. In this scenario, it is better to develop using s server hosted file, to make sure the calculations are working. For instance, Get(AccountName) is different compare to a local version and needs its own user table to convert the login name to a real username.

Regards

[Steven H. Blackwell]

For instance, Get(AccountName) is different compare to a local version and needs its own user table to convert the login name to a real username.

No.

Get(AccountName) for a user authenticated by External Server returns the Account name as defined on AD, OD, or the Server local security Groups.

Please see the External Server Authentication tech brief.

Steven

[bluearrow]

Get(AccountName) for a user authenticated by External Server returns the Account name as defined on AD, OD, or the Server local security Groups.

Steven

Hi Steven. Thank you for pointing this out. I might have not explained myself correctly.

I am currently using External Server authentication in a Windows 2003 AD domain and Get(AccountName) returns whatever the user types as user logon name. What I meant to say was that generally this logon name is not the kind of information you would like to use in fields such as Creation user, Modification user, Whatever user, etc. At least in our case, a user expect to see a real name. The user logon name in AD is not a real name (could be similar, though not identical, but most times is not). The real name is present in AD, under Properties > General tab > First name/Last name. As far as I know, there is no way to pull this info from AD to FileMaker.

[Steven H. Blackwell]

I think you can get it by some external OS level scripting and possibly by PHP, but either requires some effort.

Let me look into this a bit further.

Steven