Ted,
One other thought:
Check to make sure that you're not running into duplicate serial numbers. This could
happen either if someone went in and changed that "next serial number" setting in
field definitions, or if records from various versions of a database were combined.
Matt
At 05:21 PM 2/28/01 -0500, you wrote:
>Hey Ted,
>
>Just a few quick thoughts. Did these folks have a crash recently? It
>sounds like some kind of script corruption for the Add Names routine or
>a sub-script. Or perhaps a field corruption?
>
>Oddly, the Add Name routine just creates a new record using the FMP
>routine, then runs the Create Related Records script. At some point,
>probably the new record step, the record number isn't being created or
>updated. Then when the Create Related Records script tries to set
>subsequent record numbers for the other files (Profile, Custom, Summary)
>from the Names Record Number, they don't have a record number to use.
>I'm just guessing here, but that's the way I read it.
>
>Maybe have them check the Record Number field in the Names file to make
>sure it exists and is properly set up (i.e. indexed, auto-enter serial,
>can't modify, strict, required, unique, etc., confirm against your
>record number criteria). If it's all there, the Add Record routine
>should auto-fill that field properly in the Names file and then do the
>Create Related Records script as it should - no problem.
>
>Oh, and meanwhile, you might suggest they run the Check for Related
>Records, which will find any missing related records and create them.
>After doing that, check the Names, Profile, Summary and Custom files to
>make sure the number of records is the same for each file. If not,
>you'll have to try to figure out what ones they're missing in which
>files.
>
>Well, hope this is helpful.
>
>Carl
>
>
>
>
>Ted Fickes wrote:
>>
>> A group in the area sent me the following message and I'm wondering if
>> anyone has seen this before or has any recommendations as to where to point
>> them in terms of correcting it.
>>
>> I think the main error lies in the first part - that when they click on 'add
>> new name' they get an error message stating: "This field
>> cannot be modified until "RECORD NUMBER" is given a valid value." The fact
>> they can keep trying and get past the error message doesn't mean the problem
>> is resolved, I imagine, and the ensuing errors described cascade from the
>> first problem - I hope. They say this just started a couple days ago. The
>> system is networked and they're using FM 4.1 and ebase v1.02. Thanks for
>> any pointers.
>> - Ted
>> "the problem I'm having right now is that when I go to add a new name I get
>> an error message telling me that no new name can be added until the Record
>> Number field is filled in. This error message comes up 3 times, and then
>> after it finally goes away, it takes you to a regular data entry screen for
>> names. You type in everything, thinking that it's all fine and dandy, and
>> then when you hit "add payments" in that screen and fill in all THAT data,
>> after you hit "update status" it tells you that the record is not complete
>> until you fill in certain monetary fields, which actually ARE ALREADY filled
>> in. So, I have done this all a few times now, and then just deleted the
>> records, totally puzzled. Some background: Yesterday I was running a lot of
>> queries and exporting th edata and they were running fine. Yesterday a
>> staff member was trying to add names after I'd left and he said he found
>> "like 15 totally empty records," and he deleted them. When you go into the
>> Design mode and look for the tab that explains the properties of the record
>> number field, they are as they should be, that is, it is marked auto-number,
>> and marked that one should not be able to manually enter the numbers."
>>
>> _______________________
>> Ted Fickes
>> Environmental Law & Policy Center
>> 35 E. Wacker Drive, Suite 1300
>> Chicago, IL 60601
>> 312-795-3724
>> 312-795-3730 (fax)
>> [EMAIL PROTECTED]
>>
>> Make the List by subscribing to ELPC News at http://elpc.org/lists.htm
>>
>> The Midwest Environment Online at http://elpc.org
>>
>> ------------------
>> 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
>> ---------------------------------------------------------------------
>
>--
>Carl Paulsen
>New Hampshire Rivers Council
>54 Portsmouth Street
>Concord, NH 03301
>603-228-6472
>603-228-0423 Fax
>[EMAIL PROTECTED]
>
>------------------
>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
>---------------------------------------------------------------------
>
>
Matthew Scholtz
Evaluator and IS Coordinator
Health Initiatives For Youth (HIFY)
www.hify.com
------------------
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
---------------------------------------------------------------------
