that's interesting. i haven't touched 2007 yet either.
[btw: i just posted the articles for interest's sake (and i think TR is a good website). i don't take them to mean '07 suxorz and i won't go near it - every version has its issues.]
bob, (or anyone), don't you run into "compatibility"...
right, i wasn't really complete there. you can let the Nz function return a default automatically if you want, but you can also supply a value if Null is about to be returned.
Nz (short for Nulls) will return a default value if the item you are looking for, or calculating doesn't return anything. if you're looking up a number and the number isn't found, Nz will return zero. if you're looking for a string and don't get one, Nz will return and empty string (""). so, you...
your second IIf statement doesn't make sense.
IIf([forms]![Main]![DistrictList]="View all Districts",>0,[forms]![Main]![DistrictList])
>0 by itself doesn't mean anything. with quotes it might - ">0" - but i don't think that's what you're after.
there must be a "reference" error, meaning the name of something is wrong. maybe the code is referring to a control using the wrong name, or code in a control is referring to a field or another control using the wrong name. just check control names and field names and names used in code to make...
i think dcb said it, but to clarify a bit, the salesperson combo should be based on a query that selects only salespeople associated with the selected job. the job must be selected first. on the afterupdate of the job combo, requery the salesperson combo.
- create a query with both tables included.
- join the tables on slno
- add the field [WARRANTYDETAILS].[productcondition]
- update (update to) the field you just added to [PRODUCTINSPECTION].[productcondition].
- use copies of the tables, not the originals, just to be safe.
- delete...
dates are stored as numbers. to work with dates in code you must use the m/d/y approach, presumably because Access is made in the states. you can display dates however you like by formatting.