Data Entry

  • Thread starter Thread starter Mary Fetsch
  • Start date Start date
M

Mary Fetsch

In my Access 2000 project, I have a form in datasheet
view. When I open it now, I see all my records. I would
like to open it to see a blank form where the user can add
a new record but also query existing records. Someone
told me to change the DataEntry property on the form to
Yes and leave the AllowAdditions to Yes. When I do that,
I see my column headers, but the rest of the form is gray -
there's no place to enter data. Please help!

Mary Fetsch
 
Are you able to add new records even when the DataEntry property is set to
No?
 
Yes. I thought the point of setting the Data Entry to Yes was to open the
form with a blank record rather than seeing all your records - that's why I
did it.
 
You are right, this is the functionality of the Data Entry.

But very often with ADP, the underlying recordset of a form is Read-only, so
that it is impossible to read it or to add new records to it. Sometimes
that happen even when the direct opening of the query itself give a
read/write datasheet. (There seem to be a lot of bugs with ADP.). It's
sometime very hard to know why a form is read-only and tweak it so that it
become read-write.

But as you are able to add and to edit records when the DataEntry is set to
No, I don't have a clue at what the problem may be.

Perhaps you should try to add a WHERE clause who didn't return any record,
something like "WHERE ID = -1" or "WHERE 1=0". This is often used in ADODB
to obtain an empty recordset with properly set fields.

Also, ADP is know to be full of bugs. Maybe moving from Access 2000 to 2002
or 2003 will help. But with A2002, I have personnally found many bugs, many
of which were not corrected in the beta version of Access 2003.

ADP is like a mining field: seems good when looking at the surface, but it's
another thing when it come to work with it.

S. L.
 
Thanks for your time with this!

Sylvain Lafontaine said:
You are right, this is the functionality of the Data Entry.

But very often with ADP, the underlying recordset of a form is Read-only, so
that it is impossible to read it or to add new records to it. Sometimes
that happen even when the direct opening of the query itself give a
read/write datasheet. (There seem to be a lot of bugs with ADP.). It's
sometime very hard to know why a form is read-only and tweak it so that it
become read-write.

But as you are able to add and to edit records when the DataEntry is set to
No, I don't have a clue at what the problem may be.

Perhaps you should try to add a WHERE clause who didn't return any record,
something like "WHERE ID = -1" or "WHERE 1=0". This is often used in ADODB
to obtain an empty recordset with properly set fields.

Also, ADP is know to be full of bugs. Maybe moving from Access 2000 to 2002
or 2003 will help. But with A2002, I have personnally found many bugs, many
of which were not corrected in the beta version of Access 2003.

ADP is like a mining field: seems good when looking at the surface, but it's
another thing when it come to work with it.

S. L.


why set
 
Back
Top