Binding Text Box To Seperate Query Produces #Name Error

Rik_StHelens

Registered User.
Local time
Today, 17:00
Joined
Sep 15, 2009
Messages
164
Hi everyone,

I have a form in a database which is bound to a table containing quotes for pallets of books.

On one of the form tabs I have two text boxes which are bound to a seperate query which calculates the total Price & Quantity of the quote. Both of these text boxes produce a #Name error, although the query itself does produce the expected results.

There are then a number of other text boxes which will also be bound to further queries calculating delivery charges by location to give a total price including delivery.

What could be causing the #Name Error?

Thanks for your help.
 
Hi John,

Thanks for your reply.

Reference using DLookup() it's not something I've really used before but based on the article link I have got it working so thank you very much for your help! Much appreciated!

Is it also possible to use DLookup() to control text box output based on a query? I am creating a number of flags for UK regions & certain continents where operatives need to check shipping prices before giving the final quote. Again with this I get a #Name and now I understand the reason why, but I don't know how to get around it.

Current code as follows:

Code:
=IIf([Query]![qryGetAccountDetails]![UKCountry]<>'England' Or 'Wales','Warning: Delivery Price Must Be Checked For Rest Of UK','')

The query in question is controlled by a text box located on the form which contains the Account ID, and the address details are shown in a Sub form.

Can I use DLookUp with this and how would I structure it? Or would another function be more appropriate?
 
Never mind!

I decided it was easier to store individual instructions against each region and use DLookUp to pull these in through the Account Details query.

Thanks again!
 

Users who are viewing this thread

Back
Top Bottom