Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot seem to create a ONE to MANY relationship

Status
Not open for further replies.

FoxEgg

Programmer
Mar 24, 2002
749
AU
I must be losing it !

I have two databases in a container

PATCODE is the primary index in the first
PATCODE is a regular in the second

I click on the relationship link.. make the relationship ONE to MANY..

And Nope... it won't show me the crows foot (One to Many)

And it doesn't behave propertly on the form

Any clues gratefully receieved

John Fox
 
Stardate 23April Update

In the database container.. I can create and it shows the crows foot ONE TO MANY relationship

When I go to a form and use the database container... and add the dbc ... the CROWS foot dissappears (relationship looks like ONE TO ONE and the wacky result occurs..

I right click the PROPERTIES of the relationship and make it (check that it is) ONE to MANY.. but NOPE...

Still no good

Grrrrrr

JF

 
Well ... I deleted the second Grid (which was in a Page Frame) and re created it....

It now seems to work

I guess I must have done something funny in the page frame..

No need for assistance JUST YET

JF
 
Well ... I deleted the second Grid (which was in a Page Frame) and re created it....

You would be better off creating a parameterized view ( instead of SET RELATION ) for the child part of the on-to-may releationship amd using that to display the child records in the grid.

The reason for this is that there are many commands that can break your relation behind the scenes and result in goofy behavior.

The on-line help is quite good on thje topic of creating parameterized views.


Marcia G. Akins
 
Could not agree more.... In your situation a parameterized view is the way to go. But create it in the designer, its easier etc. Its a good idea to stick to a single name for your variable (IMO), makes it easier to populate all views i.e.
***View Filter:
<<childtable>>.Patcode = (?cMasterPatCode)

then your program can call it with
cMasterPatcode = <<mastertable>>.patcode
select <<viewname>>
=Requery()
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top