Re: Problem with Scripted Import When File is Shared, but Not When It's Single-User
- From: Howard Schlossberg <howard@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Aug 2008 17:19:45 -0700
No ideas of what might be going wrong off the top of my head. But try this:
Set the script's import step to not hide its dialog. That way you can step through the import mapping to either make sure it is still correct or to see what might have gone wrong.
jahn wrote:
I have a strange problem with a scripted import in a file in FM 9.0v3
on FM 9 Server. The file is multi-table, but for the purposes of this
script, only one table is used. Essentially the script does the
following:
1. Asks a user to identify a CSV file that has been downloaded from a
website
2. Error-checks to make sure the user has done this correctly
3. Imports the data into about a hundred fields
4. Parses the data to distribute it to certain fields and replaces
errors and inconsistencies
5. Tells the user that everything went splendidly.
On a single-user file this does, in fact, work perfectly. But on
multi-user files, not so much.
The error-check in Step 2 looks for three things after the Open File
dialog: either the user has canceled the action (error code = 1); the
import order is invalid ( = 409); or any of a number of import
problems such as wrong file type ( > 700). For some reason, a
perfectly valid CSV file that is correctly imported when the database
is in single-user mode returns error code 409 on when it's served from
FM server. Nothing has changed but that one thing. In fact, when I
disable the step that checks for error 409, the script fails to import
any data and behaves the same as if the file was an empty document. In
the import step itself, I've checked "perform without dialog" and
"specify import order" (UTF-8, matching field names), but not "specify
data source." This is to reduce user confusion, since the data
source's file name is different every time.
Any ideas? The crucial piece of information above is that the script
works perfectly on the database when it is not being shared, so
suggestions that don't take this into account will probably miss the
target.
Thanks as always for putting your heads to this.
Best,
-J.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg
FM Professional Solutions, Inc. Los Angeles
FileMaker 8 Certified Developer
Member, FileMaker Business Alliance
.
- Follow-Ups:
- References:
- Prev by Date: Problem with Scripted Import When File is Shared, but Not When It's Single-User
- Next by Date: Filemaker Pro 9 on Mac Questions
- Previous by thread: Problem with Scripted Import When File is Shared, but Not When It's Single-User
- Next by thread: Re: Problem with Scripted Import When File is Shared, but Not When It's Single-User
- Index(es):
Relevant Pages
|
