Recent content by arbasd

CJ - never mind I had something odd going on with the incoming data. Cleaned it up and all is good. Thanks again.

CJ I apologize for not being more clear in my description of the challenge and thank you for the suggestion about the field named "value". That is what the was named in the data I pulled in from a MySQL database written by someone else but I will alias it as "entered" or some such name. The...

I have the following 3 tables: Project Table = contains a unique Project_ID and Project_Name FieldNames Table = contains a unique Field_ID, Field_Name (EG: CustName, Cust St, ContractAmt, etc) and Field TYPE there are about 65 fields for each project. All the data is stored as text (even...

The PK is an autonum field? This does not prevent a "null" from being created when a user happens to enter something in a subform without entering anything in the parent form an orphan record can still created.

It also appears to me that if the Primary Key cannot be null...why would Access allow the foreign key to be null when "enforce referential integrity" is turned on? That would seem to undermine the entire purpose of enforcing referential integrity no?

Thank you. That is very informative. Wouldn't an easy way to prevent is to simply require a value in the Foreign Key? If I do that then I don't believe a null will suffice.

Sure no problem. Here you go. A simple two table one form/subform.

Access 2007...defined the relationship under Database Tools - Relationships. created the one to many relationship and clicked the referential integrity box. I then created the form/subform base on the same two tables. Try it...it is pretty simple and as long as you don't dirty the main form...

Ha ha..bitchy is a nice way to put it. Access seems to have all kinds of nuances to when it commits the record and updates the field. I am beginning to believe that unbound forms are simply easier to work with and control.

Thank you for your reply and you are exactly correct. It will create an orphaned record. Also your suggestion about checking the foreign key is perfect and much more elegant than what I came up with (simply making the foreign key a mandatory field) because it avoids the error code and allows...

Thanks for the reply but no. There was no recorded created at the main record level. The record indicator below still shows it to be a new form and the main record table does not contain a "blank" record. Yet, when I look at the table the subform is based upon, there is a record created and...

I was able to correct this by making the linked field in the subform REQUIRED so that it does not allow a subrecord to be created without FIRST having data on the main form. Although I still don't know how Access permitted a record to be created before since referential integrity was enabled...

I have a MainForm and a SubForm. I select the new record selector on the MainForm to begin creating a new record. If I then enter data ONLY in the SubForm and navigate away from the MainForm an orphan record is being created from the data entered into the subform. I do not see how this can...