By recordset, I understand that you mean a table, judging by your statement
"All my values on the record set appear as zero's as soon as any information
is inputted on the recordset"
A "recordset", in database terminology, is any set of records, whether a
table, or the result of a select query.
In fact you can set a table up so that the default value for a numeric field
is null, rather than zero, which would fix your problem, since averages
ignore null fields. However that doesnt help your current situation, unless
you want to change your table defaults, and fix up the existing data.
I dont quite understand how you have your tables set up, but you might have
to apply the "not 0" criteria individually on each field, and average on
that field alone to get the result you want. That would mean as many
queries as you have fields, which might be painful.
Are you sure your tables are normalised ? 150 fields is a *lot*
Maybe if you posted the list of fields in your tables, we could help with
some more concrete advice.
--
Regards,
Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control
Stuart said:
I have a select query, but I was unaware you could run a
recordset that would not allow zero values. All my values
on the record set appear as zero's as soon as any
information is inputted on the recordset.
I have about 150 fields that can have numbers inputted
into them. If no number is entered, the value is zero [i
need that to be blank.]
In the query, I wrote [not "0"] in the criteria, but that
did not work because if one field had a zero, then nothing
in the row would appear.
I'm not sure what to do and it is a pivotal part of my
program.
Stu
-----Original Message-----
Do a select query first to return a recordset without the zero values, then
do the average on that recordset.
--
Regards,
Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control
.
