Hi Frank,
> Can anybody tell me if this is a problem caused by the conversion from 2000
> to 2002 format, or is it a w/s environment issue ?
This is most likely a workstation issue. I suspect that the affected machine
has a MISSING reference problem. Here is more information on this topic:
Solving Problems with Library References (Allen Browne)
http://allenbrowne.com/ser-38.html
Access Reference Problems (Doug Steele)
http://www.accessmvp.com/djsteele/Ac...nceErrors.html
Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/ex...tributors.html
__________________________________________
"Frank H" wrote:
> Can anybody help ?
>
> I am using Office XP developer. I have a db (2000 format) that I wrote for a
> customer some years ago. It runs as MDB on some w/s and MDE (converted to
> 2002 format) on others - no issues at all.
> They wished to install app in another office that has 4 w/s running WinXp /
> Office XP, - according to customers, fully up to date with patches etc.
> I re-created an MDE after converting original from 2000 to 2002 format, and
> it runs without problem on three of them, but has problem on 4th (a slightly
> older notebook). Problem is simply that I get #name? in an unbound field that
> has the following as its default value : "=DateAdd("yyyy",-1,Date())". There
> is no problem if I assign this value in the forms open event.
> I created a 2000 MDE, and there is no problem at all !
> Can anybody tell me if this is a problem caused by the conversion from 2000
> to 2002 format, or is it a w/s environment issue ?
>
> TIA