Date Function Error Help Needed

[tbaguio]

Hi,

Every now and then I get a #Name? error in my database in fields where the Date() function is used. This is a quite a pain since I have forms that will not open due to important date calculations that they require. Does anyone know of any causes for this error and possible fixes for it. I've repaired and compacted the database several times, and yet the errors still remain. Your urgent help is greatly appreciated.

"Sleep is the best meditation." - Dalai Lama

 

[gwinn7]

I have seen this problem before. My experience with this problem pointed at a field that I was binding to a column in a table that no longer existed. I would suggest going back an confirming that the field you are referencing (in your Date function? whatever.) is named properly and does actually exist in the table.

If that doesn't help, could you provide a more specific example?

Gary
gwinn7

 

[MichaelRed]

Can also occur if the recodsource.controlsource is not the correct type or is null or the recordsource returns no records. I'm sure other conditions can also trigger it.



MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over

 

[tbaguio]

Thanks for all your feedback. I've figured out what went wrong... or at least a reason for what happened. I still don't have a permanent fix though.

I recently installed the Office 2000 suite on my system (co-existing with the Office 97 suite) and found out that the references for the Outlook 9.0 Object Library were screwing up my forms. When using a system with the Outlook 8.0 Object library... my database runs fine.

Any ideas on how to maintain both object libraries on the same computer with the ability to switch back and forth on demand? My understanding is that you can only use one version of a library at a time. Am I correct in assuming that?

Theresa "Sleep is the best meditation." - Dalai Lama