Export path getting confused

[eyebrown@mindspring.com]

I'm running FM Server on a dedicated Win2000 machine. There are about a
dozen users (FM 6.0) running various flavors of Windows. I have several
scripts that export text files & place them in the right place with the
right filename on the NT server that runs all non-FM work. The P drive.
These scripts having been working perfectly for a couple of months. I've
run the same scripts from the same files on three different machines. No
problems.

Now I have made a new text file export script. It only has one step,
Export Records, with file specified (leading to P drive with filename &
overwrite selected manually the first time). In every way I can think of,
it is identical (save for the actual fields being exported) as are the
scripts that work.

But when I run it, it gets confused about the path & sticks the result in
its local FM app folder. I open it, respecify file, lead it to the P
drive, and it works perfectly. I go to another machine, open the same
file & run the same script, into the app folder. Once again I respecify
and it works. But when I go back to the original machine, now *it* gets
confused and returns to sticking the export in its app folder.

I feel I'm missing something obvious, but can't figure out what it may be.

Steve Brown

[Tim Booth]

[email]eyebrown@mindspring.com[/email] wrote:

>
> I'm running FM Server on a dedicated Win2000 machine.

[... snip ...]
We are remembering that we need to make the scripts work correctly
on a local copy running on FM Pro for it to 'stick' in the
Server version of the file?

Otherwise, you can change it on each client machine, but
the next time it is opened from Server, it goes back to what
was set at the time it was placed on Server (same as with
globals in many respects)

Cheers

Webko

[eyebrown@mindspring.com]

Apologies for replying to myself. But I have received good advice and
solved my problem. The solution leads to a general observation about
hosted versus local FM databases.

Thanks to Tim (Webko) Booth, I learned that when you create a memorized
export script directly in a file being served, that the path becomes
dofferent for each subsequent user of this file. If the file were to be
pulled off the server & installed on a local machine, and the export path
rememorized, followed by reinstalling the file on the server, then the
path will have been permanently memorized and remain consistent for all
users.

Tim pointed out this this behavior is similar to that of global fields,
which become individual user fields in a served situation.

Now I begin to wonder. Are there any other aspects of FM's (6.0)
functioning that exhibit similar behavior? As pects that work one way
when a file is local, and a different way when being served?

Steve Brown