linked forms (or why Access is retarded)

[AccessIdiot]

Or maybe why my username is AccessIdiot :P

I just discovered the linked form functionality of the form wizard. I dumped the fields from two tables linked by a Survey_ID (autonumber primary key in Survey table and number foreign key in Replicate table). Access creates two forms for you with the appropriate fields.

But for some reason the Survey_ID does not get carried over into the replicate form. Access recognizes that the replicate belongs to a certain Survey_ID number because I can see in the filter property of the form [Surve_ID = 14] (or whatever number) but the Survey_ID field on the Replicate form is 0.

Why? And is there a fix? This seems very fundamental to linking forms that are linked by a primary/foreign key and yet even this very basic example fails.

Any advice/help much appreciated!

melissa

[Denburt]

I havent worked with the wizards in a while however once you review my last post in your other thread I am sure things will be much more clear if you would like to see any changes I made I will gladly send them to you.

Have a good night.

Post

[developing]

wait...so one of the forms is a subform? if yes, then add Me.Bookmark property to make sure the update takes place....

i know what u mean, for some reason, access is kinda flaky when it comes to updating linked fields in forms

[ADezii]

Or maybe why my username is AccessIdiot :P

I just discovered the linked form functionality of the form wizard. I dumped the fields from two tables linked by a Survey_ID (autonumber primary key in Survey table and number foreign key in Replicate table). Access creates two forms for you with the appropriate fields.

But for some reason the Survey_ID does not get carried over into the replicate form. Access recognizes that the replicate belongs to a certain Survey_ID number because I can see in the filter property of the form [Surve_ID = 14] (or whatever number) but the Survey_ID field on the Replicate form is 0.

Why? And is there a fix? This seems very fundamental to linking forms that are linked by a primary/foreign key and yet even this very basic example fails.

Any advice/help much appreciated!

melissa

If it is not carrying over, it is a simple matter to manually transfer over the [Survey_ID] Field from the Master to the Linked Form or to pull it from the Linked Form in its Open() Event.

[AccessIdiot]

Thanks to all who answered.

I guess I'm just flabbergasted as to WHY it's not carrying over. In the most simple case of Customers and Orders where Customer.Custom erID = Orders.Customer ID - this is like saying that for a given Customer going from the Customer form to the Orders form, Access filters on, say Customer.Custom erID = 12 but doesn't insert "12" into the Orders.Customer ID field in the Orders table. Why not? Shouldn't that be a given with linked forms? Isn't that the point of having the wizard?

Or am I missing the whole point?

Denburt I'm checking the other thread now but I am hoping to understand this as well for future projects or even for other forms within my current complicated project.

cheers,
melissa

[NeoPa]

I can understand the question, but in my experence, judging why something like this is implemented in such a way involves attention to the detail. Without knowing exactly all the selections made in the wizard, it's hard to know why Access felt that this was the appropriate way forward. It's often frustrating I know, when Access (or any other software for that matter) behaves in an unpredictable way, but it's often for reasons that are simply not understood.

Think of your own recent experience, if you look back on some of the things you've learnt recently, you'll see a number of things that make sense now which seemed totally idiotic when you first came across them.

I can't give you a definitive answer without a much better understanding myself of exactly what went down, but I'd be surprised if there weren't one.