>I'm working with a copy of ebase v1.02. This problem occurred in FM 4.1.
>converted ebase to FM 5 and the problem is still there.
Here are a couple of thoughts...
It seems to me that you have tracked the problem correctly - the
error message appearing three times means that the script "Create
Related Records" is stumbling because there is no record number in
the new record.
I would try adding a new record with a FileMaker command (menu item
Records>New Record). This should create a new record in the names
file only, and there should be a record number correctly assigned for
this new record. If there is, the FileMaker command is working
correctly. Try creating a script with only the step New Record. When
you run this script, a new record should be created in the names file
and a record number correctly assigned for this record. If it is, the
FileMaker script step is working correctly. If you have gotten this
far, I'd say the problem is in the ebase script. Try inserting Pause
steps in several places in the existing script to get it to stop so
you can review progress. You will be able to check whether the record
gets created correctly and the record number assigned, and if so,
what happens to it.
>
>Issue - when adding a new name - using the add name button - a FM warning
>message pops up. It states:
>
>"This field cannot be modified until "RECORD NUMBER" is given a valid
>value."
>
>I hit OK, it pops up again. It pops up three times. After that it dumps
>me at data entry screen 1, in the first name field - just like the add
>name script is supposed to do.
>
>Stranger yet is that there is no record number created for this record.
>It doesn't show up in any fields and, when viewing the names file as a
>table, the new record and info is there but there is no record number.
>
>I've compared the add name (and add related records) scripts with working
>versions of ebase v1.02 and see no discrepancies. The field Record Number
>is defined correctly. The field Added Correctly is defined correctly.
>
>This ebase is on a network that has had crashes before. Maybe the field
>record number is 'corrupt' but there seems to be no way to check that.
>B/c the message pops up three times, I'm guessing that the add name script
>is running up to the create related records script - which tries to create
>three records and it is those records that aren't created and are
>generating the message (3 times) which makes me think that the problem is
>occurring earlier in the script - as though the add New Record/Request
>command doesn't work. It's a FM command though and how can that be
>checked?
>
>Anyone seen this before or have recommendations for where the error could
>be occurring? Thanks much!
>
>Ted
>
>
>------------------
>Reminder to each recipient: To change your list account preferences, go to
>http://email.sparklist.com/scripts/lyris.pl?enter=support and enter
>the email address you used to subscribe to the ebase support list::
>[EMAIL PROTECTED]
>
>To unsubscribe send a blank email to [EMAIL PROTECTED]
>---------------------------------------------------------------------
> ebase - Relationship Management for Nonprofits, http://www.ebase.org
>---------------------------------------------------------------------
--
Dave Shaw Northwest Classics, Inc
tel: 206-954-7526 fax: 206-625-1338
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
