Typically, the way this is done is a bit more indirect. As FoFa said, most of the time you cannot trigger a process on another server. Particularly if you are running WinXP with SP2, you cannot do this. However, having said that, ...
If you are the administrator, you can set up a Windows Task Scheduler type thing where you can "wake up" an Access database with a macro. (See the Help for "command line options" to see how to run a macro starting from a command line.)
So... what you do is on server A, run a task that starts a Windows Script. In the script, fire off the Access macro that exports your data to a file, then fire off an FTP operation. Note that good security practices would require you to not keep the latter piece in cleartext since it will have a password in it. Keep the FTP piece as a file that gets decrypted, executed, and deleted.
OK, on server B, have a scheduled item that looks for the file you just sent. You can just run the Access macro and have it do the job in VBA. Using the File System object, find the file, import it, and then RENAME it or delete it. If you can't find the file, it wasn't sent. The key is to move all "used" files out of the way by deletion or renaming.
Don't forget to clean up after yourself if you take the renaming option. If you don't, you will run out of disk very fast.
