Enter must begin first????

[Robert Rough]

I have created a small look up table with adefault form.
Field rules such as auto increment etc have been applied to some fields.
Hit a problem however on filling the fields and sometimes get warning message
"Enter must begin first."
When this occurs i get into a cycle that I cannot close the browse or form that I am in as this message keeps popping up. Eventually having to control, alt, delete, to get out of the cycle.

What does "Enter must begin first." mean and how can I eliminate this.

Regards Robert

[metadyne]

Re: Enter must begin first????

I have had this annoying problem also occasionally.

It is usually because a previous record entry or update was tried and aborted then the table not closed afterward eg from running a script with wrong logic.

Also it can be because a set or form is damaged.

Try a database compact, exit Alpha, clear the tmp files, look for any $$M files (dictionary problem) and try it again.

[playaz2006]

Re: Enter must begin first????

DIM Shared varP_LetterheadQuote as P
DIM layout_name as c
layout_name = "LetterheadQuote"
DIM tempP as p
'Get pointer to existing window. In case layout_name is qualified with a dictionary name, extract up to first @. In case formname has spaces, normalize it
tempP=obj(":"+object_Name_normalize(word(layout_name,1,"@")))
'Test if pointer is valid
if is_object(tempP) then
'Test if pointer refers to a form or browse
if tempP.class() = "form" .or. tempP.class() = "browse" then
'If so, then activate the already open window
tempP.activate()
tempP.new_record()
else
'Window is not already open, so open it
varP_LetterheadQuote = :Form.view(layout_name)
varP_LetterheadQuote.new_record()

end if
else
varP_LetterheadQuote = :Form.view(layout_name)
varP_LetterheadQuote.new_record()

end if

Somebody suggested the above code to rectify the "enter must begin first" error message.

Can somebody explain the above in details because I'm getting the same error message when creating a new record.

I have a simple form that I use to manage my contacts. On that form, there is a "new contact" button. My problem is every time I create a new record and decide to discard/cancel the new record, I get "Enter must begin first". Sorry, I'm new to this... How do I stop this error message?

--- FYI ---

- I'm using Alpha Five 7
- I have codes in the OnSaveRecord event that asks me if I want to save the changes.

your response is greatly appreciated
thank you in advance

[Tom Cone Jr]

Re: Enter must begin first????

I have codes in the OnSaveRecord event that asks me if I want to save the changes.

This event only fires after the save has occurred. Once the save has occurred it's too late to cancel the save. Move your code to the CanSaveRecord event to see if that helps you. -- tom

[playaz2006]

Re: Enter must begin first????

Sorry, I gave you the wrong info.

The codes are in "CanSaveRecord" event.

any idea?

[gschepp]

Re: Enter must begin first????

I got the "Enter must begin first" and finally found it to be in the Field Rule section where I had Lookups. I didn't modify the table name after copying from a different table. Changing the name to current table fixed the problem.

[playaz2006]

Re: Enter must begin first????

gschepp, can you please be more specific?

Please provide an example, I'm having the same problem and I'll need your help to get it fixed.

Thank you in advance

[gschepp]

Re: Enter must begin first????

I had a new set with primary table and 5 tables linked

I copied the old set to new set.
Deleted the old links to old tables.
Relinked new tables to primary table in the new set.

Then had the Enter must begin first problem.
It was in the field rules section. I used Lookupc function in Field Types with Calculated and entered the Lookupc expression in the Calculated field expression box. The specific expression was LOOKUPC("F",GA_IDX,"Last","general_assembly","ga_Id")
which should had been
LOOKUPC("F",GA_IDX,"Last","state_house","ga_Id")

general_assembly being the old table and state_house being the new table.

You might also isolate/determine the problem in the Trace Window/View Events