Michelle,

Maybe you should tell us more about this "network" where this seems to happen, like what make/model/version is it, running on what processor, commected to what processors/op-sys' etc.

Most of us do network apps and do NOT have the kinds of problems you describe here from time to time.

good luck

Jim N

>>Michelle,
>>
>>It's certainly possible to do what you describe. The main advantage of this set up is that maintanence is easier (you only have to update the executable on the server, not on each workstation). I doubt, however, that it will solve any of the problems you're having. The only thing that should work differently is that you need to make sure you've either set the default or set the path to the data when the executable is on the workstation.
>>
>>I doubt the skip message is getting "lost" between the workstation and the server. If your network were that bad, you'd be losing all kinds of things. Even if that is happening, putting the exe on the server won't help. The workstation will load the exe from the server and all the data will still have to be sent back and forth between the server and the workstation.
>>
>>Of course, it won't hurt to try it. The biggest disadvantage is that you'll have increased network traffic when a workstation loads the exe and the application may run a little slower.
>
>Hmmm... It sounds like that won't help.
>
>I wish I knew why it doesn't skip properly on a network!
>
>Thanks,