Lorna70
asked on
#Name? in Date field
Hi
I am converting a client's current system from MS Access to ASP.Net. My client has given me an .mde file which I have set up in my development environment and configured to access a SQL server database. I need to be able to play about with these forms in order to fully understand the current system, however the forms which contain a date field have the following error: #Name?. I have searched the web for a solution and I'm told that this is a VB References problem which I cannot resolve because I cannot access the VB code. Is there anything else I can try?
I am converting a client's current system from MS Access to ASP.Net. My client has given me an .mde file which I have set up in my development environment and configured to access a SQL server database. I need to be able to play about with these forms in order to fully understand the current system, however the forms which contain a date field have the following error: #Name?. I have searched the web for a solution and I'm told that this is a VB References problem which I cannot resolve because I cannot access the VB code. Is there anything else I can try?
YohanF
That could be because the table that form/field links to doesnt have the corresponding record.. Try understanding the table structure and may be add the relevant records before trying it out/..
Generally this error indicates that the underyling Recordsource for the form (i.e. the Table or Query on which the form is based) doesn't include that Field/Column. It could also be that the Field/Column was using an Access-specific function, or referring to an Access object (like a Form) and when you moved it up to SQL Server you broke that portion of the code.
It could also be a Reference issue, but that would be less common. In that case, you can "read" the references from a .mde file. Here's a link to a small utility that'll do it:
www.infotrakker.com/progsamples/accessreferences.zip
If you're simply trying to understand the system, then what is the point of upsizing it to SQL Server? just leave it connected to the .mdb datasource and review it that way.
It could also be a Reference issue, but that would be less common. In that case, you can "read" the references from a .mde file. Here's a link to a small utility that'll do it:
www.infotrakker.com/progsamples/accessreferences.zip
If you're simply trying to understand the system, then what is the point of upsizing it to SQL Server? just leave it connected to the .mdb datasource and review it that way.
ASKER
Thanks YohanF but it occurs in forms for entering info so the date field isn't linked, I think it's for data entry. Thanks LSMConsulting - to make it clearer, it's an Access Front End onto a SQL backend. I managed to get it linked and working (partly) with the SQL backend, it's just that I can't try entering info to see how they work until I resolve this.
It may not be linked to a table, but could be looking at another form.. Access can very very confusing when its not done in a properway.. so I understand...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well yes I am getting lots of different errors including the one where Access decides to shut itself down without my permission lol! Thanks - I've downloaded the References file but what do I do with it and will I be able to resolve it without the mdb file?? My client has paid for the IP rights for it but the company has gone bust and he says he never got the mdb file.
Mate, try this. I wouldnt guarantee this would work but if it does you are a winner.
You said its a date field ya. Just open up normal access database and add a reference to this file using the VBA end.
After that, give opening your mde again and it may work, may not. If it does you are sorted, if not we'll think of another way.
cheers
datime.dll
You said its a date field ya. Just open up normal access database and add a reference to this file using the VBA end.
After that, give opening your mde again and it may work, may not. If it does you are sorted, if not we'll think of another way.
cheers
datime.dll
ASKER
Hi Yohan Sorry for appearing a bit thick but not being a VB or access programmer, I'm not sure what you mean. Please can you give me more basic instructions :-)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks LSM. Done that and I'm told that my DB contains missing or broken references to file MPEU83.tlb version 8.3. I don't know if I can do anything about this as when I open the VB editor and go into Tools, References is greyed out - any ideas or should I just give up now?
ASKER
I've just realised that this is still open but I never resolved it. Given that the problem only lies with date fields, and the Access front end works at my client company, it must surely be a pc specific problem? I am using Access and SQL on the same pc - could it be that one is set as UK and the other US and this is causing the conflict?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.