one-to-many to one-to-one

ezfriend

Registered User.
Local time
Today, 03:17
Joined
Nov 24, 2006
Messages
242
I have a main form and a subform that was originally design as a one-to-many relationship. Now the users want it to be a one-to-one relationship.

The logical way is probably moving all of the fields in the subform to the table where the main form is loading from. For one db, it is probably not a big deal, but I have serveral databases that are like that so it could be time consuming to move fields and data from one table to anther.

Question: What's the easiest way for me to manipulate the form so that once the subform has the first record, the subform is locked for adding more records? If no subrecords, the subform's Allow Addition should be true. * User should be able to edit the subrecords as they would on the main form.

Any advice is appreciated.

Thanks.

EZ
 
I have a main form and a subform that was originally design as a one-to-many relationship. Now the users want it to be a one-to-one relationship.

The logical way is probably moving all of the fields in the subform to the table where the main form is loading from. For one db, it is probably not a big deal, but I have serveral databases that are like that so it could be time consuming to move fields and data from one table to anther.

Question: What's the easiest way for me to manipulate the form so that once the subform has the first record, the subform is locked for adding more records? If no subrecords, the subform's Allow Addition should be true. * User should be able to edit the subrecords as they would on the main form.

Any advice is appreciated.

Thanks.

EZ

If the existing Dataset has One-to-Many relationships, a new Dataset will have to be created that does not have One-to-Many relationships. What will be the determining factor(s) for deciding which of the Many will no longer be supported?
 
Your users sound as if they have their heads up their...well, you know!

What lame excuse are they using for this request? Perhaps if they could explain why they thought this was necessary it would be easier addressing their concerns! Granted I am somewhat of a maverick, but when end users have insisted on something this absurd to me, I've always suggested that perhaps they should create the database themselves, since they apparently had more knowledge than I did! And to a man they always backed off!
 
when you say one-to-one do you mean the subform should not be a continuous form, but be a single form

there's no problem with that - the problem is if they are saying the RELATIONSHIP between the two forms should be one-to-one - which is distinctly unlikely
 

Users who are viewing this thread

Back
Top Bottom