By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,454 Members | 2,609 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,454 IT Pros & Developers. It's quick & easy.

DATE() does not work on Windows 2000

P: n/a
In my application on Access 97 I have users on OS: Windows NT and Windows
2000.

When I compile the MDB file on Windows NT, all the queries in the MDE file
does not work if I am using the DATE function. (Excample >Date() in a query)

I have put some systemfiles like comdlg32.ocx; comdlg32.dll; comcat.dll;
Dao360.dll in the same catalog but it does not work.

I found that this was necessary becase when I looked in a mode on reference
som of them where missing.

I am very frustraited and hope some out there have a good advice on this
problem

Helge
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Danke wrote:
In my application on Access 97 I have users on OS: Windows NT and Windows
2000.

When I compile the MDB file on Windows NT, all the queries in the MDE file
does not work if I am using the DATE function. (Excample >Date() in a query)

I have put some systemfiles like comdlg32.ocx; comdlg32.dll; comcat.dll;
Dao360.dll in the same catalog but it does not work.

I found that this was necessary becase when I looked in a mode on reference
som of them where missing.

I am very frustraited and hope some out there have a good advice on this
problem

Helge

Here are my top 3 references in A97, in the order they appear in the list.
Visual Basic For Applications
MS Access x.x Object Library
Microsoft DAO 3.?? Object Library

Open up a code window and check the references and their order.

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.