Hi,
I have a mixup rally going on with Library References in my Access VBA Application. I developed the application that someone at work now uses daily. that person made a slight change to the text of an email that goes out from the application through Outlook OLE Automation. EVersince then, all the Date() calls in the application do not get recognized unless we add Microsoft Word 9.0 Object Library to the library References. Now, the problem is that the same database is accessed from two different client computers for data-entry work off a file share. One of those computers has MS Access that doesn't have the Microsoft Word 9.0 Object Library Reference in it. so, the Date calls are not recognized whenever the Access application is run on that computer (off the file server ofcourse) and they show up as #Error#.
Now what do I do? I'm really confused about these whole references deal and their discrepencies. Shouldn't it all just matter on what references are set on the main fileserver copy of Access where the application actually resides. or shouldn't the client applications use the server's installation/resources to resolve all of its references.
just for the information, the other references that the application has are
Visual Basic for Application
Microsoft Access 9.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft Outlook 9.0 Object Library
Frankly, why has the date() started requiring the Word library reference in the first place. What's that got to do with date?
Thanks.
Saad