dblodgett

It's definitely a workaround, but you could name the fields in question as objects, then use the "go to object" script step, which can be populated using a variable. Hope that helps. DB

Thanks for the suggestion. Doesn't seem interested in putting a backup on the system drive anywhere but the default location. When pointed to another drive (duh), the scheduler was much more cooperative. - Chagrined in CT

Hello, group, While any backup schedules pointing to the default folder work flawlessly, I am unable to get server to validate a path to a folder I create. Ex: [color:green]filemac:/FM9 Server HD/Library/FileMaker Server/Data/Backups/Sunday/ is not seen as valid. I have tried a number of different locations on the HD, with and w/out the slash, to no avail. What am I missing? Thanks! Dave Blodgett

Thanks for your thoughts, everyone. FM support seemed to think that there might be a slowdown in traffic since they use the same port, but I'd be surprised, considering the miniscule traffic we generate. I will get that 5.5 server up to v.4, jd — thanks. What a great resource this is! DB

We currently serve out about 8 solutions, half of them relational, using FM 5.5 server on a G3 tower running Classic (9.1). Works great. I am retooling a G4 Panther server to run FM 8 server to make the transition to OS X, but still need to run 5.5 for the next few months anyway. In experimenting with some of the 8 solutions (which are working well), I noticed a significant slowdown on the 5.5 side, and I suspect it caused 5.5 server to lock up. Does anyone know if it is ill-advised to run two servers on the same network? I was under the impression that the protocols had little in common. Thanks for any ideas. Dave