Tanya

In my limited experiments, positioning and sizing one dialog window determines positioning and size of all future ones, across all files, in a local or networked environment. Beyond this (and it might not be reliable), there is no logic. Thankfully, there are many plug-ins that provide dialog control.

Stringing along attachments isn't working - Entourage doesn't understand why it's getting a separator followed by (what it sees as) gibberish. Does anyone have anything to say about possibility of creating mail message with first attachment and running second script to ADD attachments one at a time? Fenton - where can I find Entourage's Applescript dictionary? Thanks!

ScriptBuilders was my first stop, not many scripts for the simple task of sending mail. By the way, a directory can be attached (which is helpful) - Entourage compresses it into an archive using your prefs. I'm trying to attach multiple files that will appear as individual files (i.e., display in a savvy email app). Thanks again.

Thanks! Last thing with this script: multiple attachments! How should a second, third etc attachment be added to my emailattachment field? First attachment looks like this and works like a charm: HD:Applications:FileMaker Developer 7:EmailImages:example1.jpg Thanks.

I'm getting stuck with a "where is the application?" dialog. Can anyone help me eliminate it and improve my script? Thanks. "tell application " & """ & "Entourage" & """ & "

FM7 has a serious bug (see post on importing records) whenever a script step has a specify file button. FM calls the reference to the file an "unnamed reference" and results are wacky. All FM documentation -- and the "specify file" dialog -- say you can attach multiple files. You can't. Documentation also says that the import records script step works in network environment. It doesn't. Also, when you export the container contents, be sure it's to a local relative path, or FM may not be able to locate it (even though documentation says it should).

This is partially to seek help and to politely request that responders not chime in without carefully reading the post (hint: if your "advice" includes the word "should," reread the post). The "send mail" script step does not a) allow attachment of multiple files due to "unnamed reference" bug (see post on importing records); : allow a user to attach ANY files without editing a script (programmers edit scripts, not users); c) send mail script step does not send mail, it places the message in the outbox or, on Mac, drafts. Only on Windows is a user left at open mail message if "perform without dialog" is not selected. I am seeking to have a script send the message w/attachments (really send it) or to take user to the open message in the email application, so they can attach files and/or click send. Essentially, I am seeking working Applescripts/VBscripts that can be called by FM script. Thanks!

I would love some help with cross-platform FM->Entourage/Outlook task. I know Applescript/VB script can handle this, but my scripting is poor. All I want is to send a mail message to Entourage/Outlook with to, from, subject, body and ATTACHMENTS. Or, worse case, no attachments, but an open window in Entourage/Outlook all ready to SEND is my goal. Thank you!

Although not a conversion ("migration") issue, the phenomenon of UNNAMED REFERENCES is discussed, as far as I can tell, only in the big migration white paper. (In the white paper, of course, they are supposed to work.) Unnamed refs are file refs that, rather than being stored in the file refs place (define file references) are stored in or with scripts (?). These orphaned file refs are created each time you use the "specify file" script step (import, open, etc) - thankfully not when using "perform script/external script" step. On a network, specifying fmnet:/IP/filename.fp7 works properly (i.e., correct file, file's current found set), but using the wildcard "*" [asterisk] in lieu of an actual IP results in what Bailey Kessing reports above (i.e., correct file, ignores found set). On a single machine, everything works like a charm, so developers get to wait until testing on a network to discover this zany bug. I am recommending to my team that any time they see that "specify file dialog" when writing a script to think of another way. To see this bug (or some variant) in action, write a send mail script and try to specify more than one file as an attachment. The usual dialog states that one or more files can be specified with the add button or by typing paths. Even with an absolute path (IP, not "*"), files simply are not referenced beyond the first one. This is a HUGE bug that FM seems to want to treat as a migration issue. It isn't. Make a fuss so we get a fix soon!

No, this really is a major bug in FM7. We have now spoken with two rather high-up manager types at FileMaker support and they have said it is a bug being worked on in the next update. (Hopefully they know what they are talking about. Sometimes i feel like I know more about FM than they do.) Yes, I experienced the problem with it only importing ALL records from a file. Seriously troublesome - the import script should allow you to select a specific found set and transfer those records from one file to another using "import." This is how it worked in previous versions of FM and is supposed to work this way now as it's the main way to move records from file to file. Specifying the data source is not helpful for a commercial solution like ours (it may be fine for a one company solution) because we will be installing the same set of files for over 300 of our clients. These clients vary from one computer systems (no server) to 3 computer systems (no FM Server) to 30 computer systems (using FM Server.) We cannot build a solution that needs us to go in and enter the IP address for EVERY import script in the program (there are about 30 of them) for all 300 different clients. Solution? We have decided (and were recommended to by the FM support managers we spoke to) to not use the import scrip step at all! We are using a work around which is much slower but works: we create a relationship between the two files based on an arbitrary serial number and have the program loop through the records in the main file, pasting info in to a portal to the related file to create new records there. If anyone has a better solution I'd love to hear it. It really seems that FileMaker blew it on this one...

HELP! In migrating my FM6 solution over to FM7 it seems that I have to specify the IP address in all scripts that use the "import records" script step if they are a client on a network with a remote server. This is terrible news for me as I use the solution for hundreds of different clients, all with different Server IPs. My question is: A.) is there a way to specify that I want the import to simply look for the file's name (locally or remotely) - this is how it used to work in FM6 OR B.) is there a way to make it based on a calculation that would go and look for the IP address of the server (if there is one)

I've got three clients who are using OS X and FileMaker Server 5.5 and who are all experiencing crashes and data loss. Can anyone tell me what the problem is? Help!

Previews of printing layouts do not correspond to actual printouts. This problem has plagued me for many moons. Any ideas? Fixes?null