I was wondering if anybody had a similar situation and how you handled
it:

We create a daily newsletter db for a client. To manage these
newsletters, we created a filemaker database and will give it to them.
They will be running a runtime solution on their computers.

Each newsletter has many topics and subtopics associated with it, as
well as a specific volume and number.

As it is now, once a week we send them 7 pdfs and they store them
wherever they want. They use no database, so they can't intelligently
search for the newsletters to reuse them (it is a safety newsletter,
so they want this capability).

I want to create a filemaker "update patch" and email it to them once
a week with the pdfs in container fields and all of the newsletter's
information (volume, number, date to distribute, and the topics/
subtopics) for the following week (7 in total). I am going to put an
"update" button in their runtime solution where all they have to do is
click on it to insert the 7 new newsletters in the database.

My big problem: the Import in a script wants a SPECIFIC file location
for the update patch in order for me to automate all the matching
necessary. I can't have an "open file" dialog box for the client to
select the update patch they just downloaded?

Any Ideas? I have a sneaking suspicion that I am tackling the problem
all wrong, so any advice would be helpful.

Thanks in advance

On May 10, 7:16 pm, EP <ericp... (AT) gmail (DOT) com> wrote:

You can put the update files inside the runtime solution's main folder
or a subdirectory within it. When you create the update script, it
will be able to use the the files' relative location, so just instruct
the end users to copy the update files to the predefined location.

-Scott in SoCal