New date record not appearing in a form

Hello,

When I add a new data record through a form or into a table, the data is not
visible when I open the form later. Access does sense that the entry is
there because it rejects another attempt to create the data with a message
about creating a duplicate primary keys.

What am I doing wrong?

Sincerely,

Isaac

Did you look in the table to see if the data is there?
The MS Access message refers to only the primary key being a duplicate.
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".


"Isaac P." wrote:

Hello,

When I add a new data record through a form or into a table, the data is not
visible when I open the form later. Access does sense that the entry is
there because it rejects another attempt to create the data with a message
about creating a duplicate primary keys.

What am I doing wrong?

Sincerely,

Isaac

I checked, and the data is indeed there. It appears that the query or the
form is not picking up the new entries.


"Dorian" wrote:

Did you look in the table to see if the data is there?
The MS Access message refers to only the primary key being a duplicate.
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".


"Isaac P." wrote:

Hello,

When I add a new data record through a form or into a table, the data is not
visible when I open the form later. Access does sense that the entry is
there because it rejects another attempt to create the data with a message
about creating a duplicate primary keys.

What am I doing wrong?

Sincerely,

Isaac

In Design View for your form goto

Properties - Data

and set the Data Entry Property to NO.

Data Entry set to YES means you can ***only*** add new records, you cannot
view existing records.

While there, make sure that

AllowAdditions
AllowEdits
AllowDeletions

are all set to YES.

The Data Entry thing is always confusing to newbies as it is ill-named!
Should be a more descriptive name. like EnterNewRecordsOnly.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

Thank you for the suggestion. I checked those items, but they were already
set to what you suggested.

For some background, this database used to be an Access 97 database, which
was converted to Access 2000 file format.

Isaac

"Linq Adams via AccessMonster.com" wrote:

In Design View for your form goto

Properties - Data

and set the Data Entry Property to NO.

Data Entry set to YES means you can ***only*** add new records, you cannot
view existing records.

While there, make sure that

AllowAdditions
AllowEdits
AllowDeletions

are all set to YES.

The Data Entry thing is always confusing to newbies as it is ill-named!
Should be a more descriptive name. like EnterNewRecordsOnly.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

Hello,

I found a solution to the problem. The form was using a query that was
pulling data from two tables. While entering data into some fields in the
form or directly into one of the tables, the query or the form wasn't picking
up the entry because (as it seems to me) the new entry did not contain data
in both tables that the query was pulling from. So, I made sure I filled in
all the fields with something, causing both tables to have data for that
entry, and that solved the problem. Now the entry appears in the form.

If I were to re-do this database, I would not use two tables for this set of
data. I would simplify things by just using one table. O the value of
simplicity!

Thanks for all your suggestions.

Best regards,

Isaac

"Isaac P." wrote:

Thank you for the suggestion. I checked those items, but they were already
set to what you suggested.

For some background, this database used to be an Access 97 database, which
was converted to Access 2000 file format.

Isaac

"Linq Adams via AccessMonster.com" wrote:

In Design View for your form goto

Properties - Data

and set the Data Entry Property to NO.

Data Entry set to YES means you can ***only*** add new records, you cannot
view existing records.

While there, make sure that

AllowAdditions
AllowEdits
AllowDeletions

are all set to YES.

The Data Entry thing is always confusing to newbies as it is ill-named!
Should be a more descriptive name. like EnterNewRecordsOnly.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

Then something is apparently off in your Query. Can we see the SQL for your
Query that the Form is based on?

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

That's what I figured after your previous response. An Inner Join performs
exactly as you've just described, and is the Default if you do not set a
different join type.

Glad you got it figured out!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/200910/1

Sure, here it is:

SELECT DISTINCTROW Customers.CustomerID, Customers.[Full Name],
Customers.Type, Customers.Status, Customers.[PO Box], Customers.[Street
Number], Customers.[Street Name], Customers.[City/Town],
Customers.[Province/State], Customers.[Postal Code], Customers.Country,
Customers.[Contact Name], Customers.[Telephone 1], Customers.[Telephone 2],
Customers.Fax, Customers.[IRS #], Customers.[Email Address], Customers.[Web
Site], Customers.Notes, [Financial Details].[Credit Limit], [Financial
Details].[Rubber Plow Discount %], [Financial Details].[Steel Plow Discount
%], [Financial Details].[Replacement Part Discount %]
FROM Customers INNER JOIN [Financial Details] ON Customers.CustomerID =
[Financial Details].[Customer ID]
ORDER BY Customers.CustomerID;



"Linq Adams via AccessMonster.com" wrote:

Then something is apparently off in your Query. Can we see the SQL for your
Query that the Form is based on?

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com