What about going in to the query criteria and putting is not null? Or better
yet, go into the form itself and don't allow the user to enter a null value?
--
Milton Purdy
ACCESS
State of Arkansas


"ffulmer via AccessMonster.com" wrote:

Hi All,

I have created an application that among other tasks will convert currencies
into a base currency.
The user selects a base currency then enters amounts in different currencies
into a form.

QUERY 1 gets its data from the underlying table and shows only records with
the selected base currency.
…
WHERE (((qry_BdgOthers.CurrencyID)=[BaseCurrency]));


QUERY 2 does the opposite. It gets its data from the table and returns
records that are not base currencies.
…
WHERE (((qry_BdgOthers.CurrencyID)[BaseCurrency]));

After converting the non base currency into base currency another query adds
the Totals together.

The trouble is if either of the 2 queries is null I cannot do that.

How to solve this problem? At which point to solve it? In the first 2 queries
or when I add them together?
The field names in the queries come from the table. I don’t know where in the
queries I could use Nz(), or how to replace the null value with a zero value.

Anybody has idea?

Thank you

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...eries/201005/1

.