It is required because file needs to travel by email. I don't want to
transfer the entire database because not all file data is to be shared.
oh, you neglected to mention that!!! Significant information.
To export the file, use TransferText to output it to a delimited
format, and give it a standard name.
Then you could use Outlook/MAPI automation to e-mail the file you
export.
ON the other end, you could use something like Danny Lesandrini's
InBox Watcher (
www.amazecreations.com/datafast) and if there's a
message from Email address "X" and with subject "Y" and attachment
"MyOutputFile.txt", you could detach the file to a directory, import
it, and then delete it. The user would have to set up the import
once, mapping the path to the file and the fields in the text file to
the table, but that's about it.
Okay...pseudo-code... Sender side...
1. export the file - use TransferText
2. Create a new e-mail message (automate Outlook or Outlook Express or
use CDOSys or..)
3. attach exported file
4. add .To and .Subject and .Body information.
5. send message
6 optionally close Outlook (use IsAppRunning to determine whether to
close it).
pseudo-code for Recipient side.
-use InBox watcher to poll inbox.
if message exists meeting criteria,
- save the attachment somewhere,
- quit Outlook if it was not already running
- use TransferText to import it using a saved import specification
- do something with the imported file (move it/delete it so it does
not get processed again).
You could store the path to the file in a custom property or a
table... depends on how you want it to work. Okay, that said, how
comfortable are you with VBA?
