#Name? Errors - Please Help

[kensaffer]

Scene:
Using Access 2000 upsized to SQL Server from MDB. HAve text box's on form that when single clicked put todays date in, when double clicked sets date to null(clears out the date). Works fine in mdb version. After upsizing the first two text box's work fine in SQL server but the rest of the box's are filled in with #NAME? and I'm asked if I want to debug.

Reading help for what #name? means indicates a possible missing DLL - But why would the two text box's work ok if it's missing a dll ?
Anybody have any ideas ?
I rechecked the forms and properties and verified there seems to be nothing different between the two and the others.

 

[PaulBricker]

I don't know if this will help, but I just upgraded an Access 2000 db to 2003, and some of my unbound date boxes acted the same way. I opened a vba module in design view (any module in the db should do, new or existing) and then on the tool bar went to Tools...References. There was a library marked as "Missing". I unchecked the box next to that library, and exited out of the Module, and everything worked fine after that. So start by looking to see if you have a missing module. If it is, uncheck it and see if that helps.


Paul

 

[payback]

Check to see if you have used any reserved words for the fields in your tables. The converter will process your original Access names and accept them or change them to a valid SQL name, but you will not be able to use them in the SQL version's forms. It is possible that the first one it hits in a table or query will throw errors in other controls also.

In my experience #Name usually occurs when a form has a bound control pointing to a field that does not exist, or some typo in a calculated control.

 

[kensaffer]

Thank you for the tips. Access 2000 does not provide a 'missing' reference. When I click on help for #name? error it says a possible missing MSOWCF.dll, I searched for it and it was already checked off in references. So that doesn't seem to be the remedy.
Snippet of the code that works is very simple...
Single click = put in current date and double click is null it out
------------------------------------------------------
Private Sub PhotoID_Date_O_Click()
PhotoID_Date_O = Date
End Sub

Private Sub PhotoID_Date_O_DblClick(Cancel As Integer)
PhotoID_Date_O = Null
End Sub

-------------------------------------------------------
This one doesn't work....
Private Sub BC_Date_R_Click()
BC_Date_R = Date
End Sub

Private Sub BC_Date_R_DblClick(Cancel As Integer)
BC_Date_R = Null
End Sub
--------------------------------------------------------
Any other ideas that might point me in the right direction ??

 

[PaulBricker]

I assume that is the Microsoft Office Web Components Functions Library. Go in and UNCHECK the library. Exit out of the Module, and see if things work. If they don't, then go back in and recheck the library and check it again. Often times, you have to uncheck a library for the problem to resolve itself.


Paul

 

[cmmrfrds]

Replace Date with Now

This one doesn't work....
Private Sub BC_Date_R_Click()
BC_Date_R = Now
End Sub