one to one annomly or built in feature of access?

[bbrazeau]

I have a one to one relationship between tables Rfqs and Quotes.
I have a form "frmRfq" that has a button "cmdNewQuote" it opens the "frmQuotesAdd" with:

Private Sub cmdNewQuote_Click()
If DCount("QuoteID", "tblQuotes", "QuoteID =" & Me.RfqID) = 0 Then
DoCmd.OpenForm "frmQuotesAdd", , , , acFormAdd
Else
MsgBox ("This Rfq already has a quote")


End If
End Sub

When I run the code I get a dialog box similar to a parameter query asking for the Rfq. My question is...Is this something access does automatically with a one to one relationship or is there a mistake in my code? P.S. I use the On Load event of "frmQuotesAdd" to set the QuoteId to the current RfqId.

Private Sub Form_Load()
Me.QuoteID = Forms!frmRfqs!RfqID
Me.Form.AllowAdditions = False
End Sub

[pbaldy]

The parameter prompt usually means something is spelled wrong. It's Access' way of telling you it can't find something.

[ssanfu]

I have a one to one relationship between tables Rfqs and Quotes.
I have a form "frmRfq" that has a button "cmdNewQuote" it opens the "frmQuotesAdd" with:

Private Sub cmdNewQuote_Click()
If DCount("QuoteID", "tblQuotes", "QuoteID =" & Me.RfqID) = 0 Then
DoCmd.OpenForm "frmQuotesAdd", , , , acFormAdd
Else
MsgBox ("This Rfq already has a quote")
End If
End Sub

When I run the code I get a dialog box similar to a parameter query asking for the Rfq. My question is...Is this something access does automatically with a one to one relationship or is there a mistake in my code? P.S. I use the On Load event of "frmQuotesAdd" to set the QuoteId to the current RfqId.

Private Sub Form_Load()
Me.QuoteID = Forms!frmRfqs!RfqID
Me.Form.AllowAdditions = False
End Sub

Since the two tables have a one to one relationship, why do you have two tables? One record in tblRfqs can have one, and only one, record in tblQuotes.

Or why don't you have a query that joins both tables and display the fields on one form? No need to waste time with DCount() or opening another form.

It would be different if it was a one to many relationship, where there could be more than one quote for each Rfq.

[bbrazeau]

The reason I chose to split Rfqs and Quotes out into 2 tables are:
1).They will be created by different people at different times and will each have an author and date fields of who made what and when.
2). Quotes will be a complex table and form with links to other tables that would have made working with Rfqs that much tougher. I'm not that good at programing.
3). I will eventually make a query that pulls Quotes and other tables together, and maybe have Rfqs as a subform, but I want to keep Quotes (filled in by hopefully a skilled user) seperated from Rfqs (filled in by someone of potentially far less skill and potentially a far greater propensity for messing something up.

I just made a simlified example and everything works fine. I'll find my mistake in the code. Will "DCount" put that much of a performance hit on my database?

[pbaldy]

As you're using it, the DCount shouldn't be a problem. They're worst when used in queries.