db gone mad?

[Bob Arbuthnot]

I have a time clock program I developed last Spring that we've been using at my business since June without any problems. Suddenly I'm beset with a dysfunctional program that gives me a lot of the following messages:

"Enter must begin first."

"Data entry already in progress."

"Save enter in progress?"

I've attached the offending (offensive) data base in a zip file. Please take a look and see if you're getting what I'm getting. These messages come up even when using the default browse or form. I've tried compacting and rebuilding indexes and am out of ideas. Anyone?

[Keith Hubert]

RE: db gone mad?

Bob,

Attachment, what attachment?

RegardsKeith HubertAlpha Guild MemberLondon.KHDB Management Systems

[urbanski]

RE: db gone mad?

When I run into these messages, it means that the database is ecpecting you to enter some data -- usually a require field -- at a point where you were tying to do something else or might be trying to leave the screen where the data entry is require. Often it is a set design issue.

Jim

[jdtwright]

I had this same problem. To fix the error, I went in to my table field rules and made sure that all fields that are used in a calculation had a default value set. Once I did this, the problem went away for me.

[Lance Gurd]

I occasionally get these messages, which is a pain. As I have to close the form and enter the data manually into the default browse.

My only calculated field on this form has a default value which has been set by Alpha

[martinwcole]

you also get this kind of error if you have xbasic code that is firing when you push a button, for example, and the form is in an enter/edit mode

like t=table.get("parenttable")
t.change_begin() - will cause this kind of error if the form is not in a view (record was not previously saved) mode

you can say this:
parentform.commit()
t=table.get("parenttable")
t.change_begin()

also - since Alpha in all versions I am aware of since 4.0 will occasionally cause the form to advance to the first or a different record using "parentform.commit()", I typically use code like this:

dim rnum as n
rnum=table.current(1).recno()
parentform.commit()
if table.current(1).recno() <> rnum
parentform.index_set("")
parentform.find(rnum)
end if