beta Server and IP address matching

[MorFologist]

In FM5/6 I found it crucial for my Windows clients accessing the server from another LAN, that I use the same static IP address on my own server as the one at the client. Saved me the headache of testing and relinking scripts, plus it was snappier if the script "remembered" the IP.

Does the same hold true under FM8?

[Wim Decorte]

No, in FM7/8 you have full control over the file references.

When you define file references in 7/8 make sure to change them to the best format for your deployment. You can even add multiple references to the same file, in different paths.

file:theFile.fp7

is likely to be the best reference if all files are on the same FMS.

[MorFologist]

Thanks. Was that a file you were attaching?

I guess the IP address is not the only issue. I went back to a regular DHCP (hmmm) address off my router, and server admin now works locally on the server machine (yea), but remote from my workstation, I still get a "lost connection". Not a big deal, it gets me out of my chair! Just happy to know I can clean up my file refs manually now. I got a good laugh at the list from the converted FM5 files... Memories!

[Wim Decorte]

No, the "file:theFile.fp7" is how a file reference in its simplest form looks like. If you have the file refernce in file A then FM will look for theFile.fp7 in the same location as where file A is.

[Vaughan]

The server should have a fixed IP address. Get it off DHCP.

File references is a different issue. Wim is correct in what he says about them.

[Vaughan]

The server should have a fixed IP address. Get it off DHCP.

File references is a different issue. Wim is correct in what he says about them.

[MorFologist]

"file:theFile.fp7" Sorry, that was so short compared to the ones in my report I didn't recognize it!

What I'm thinking is, before transferring the files to a client server, I would need a format like this, using their server IP:

fmnet:/10.100.18.200/JobType file:JobType.fp7

so that it can work across several routers and the WAN.

Not true?

I was assuming the lack of targeted IP would lead to confusion or broken scripts, especially if there was more than one FM server on the LAN. There will be several in the company, with my users in several locations with some connections across a T3. I myself will be on the other side of that T3 from the server!

This is just based on my experience with developing on a Mac on site for an FM5 system: If, in a script, I didn't make sure the IP showed rather than "*", it was slow to open referenced files for the PC users, and scripts on the desktop launch file would not work for them at all.

[color:gray](The "beta" server is just my 2nd computer in my home office, but so as not to get it confused with Tivo, I'll give it a static number once I have files to test on it. I was trying to make it the client IP without having to redo the rest of the network).

Thanks!