General

Re: Important Issue

Shiraz Cupala — Sat, 12 Aug 2006 03:05:58 GMT

Fantastic mbenbow. This information will be very useful! Thanks for contributing.

Re: Important Issue

mbenbow — Fri, 11 Aug 2006 14:22:03 GMT

The link below can be useful is it is a versioning issue for a DLL.

http://support.microsoft.com/dllhelp/

MB

Re: Important Issue

nukkumatti — Fri, 11 Aug 2006 14:00:32 GMT

Oh and another post already just while I was writing mine.
Thx mbenbow. I guess this is also useful for them.

Re: Important Issue

nukkumatti — Fri, 11 Aug 2006 13:58:26 GMT

Hi Matt,

thx for the fast reply. I forwarded your post to our Technical Center (Helpdesk) and may be also have to wait for information form Bolton (main facility, hope their weather is better than ours here in Luxembourg :) ). I'll come back to you if I have some news and gonna post the solution anyway (hope we can find one) so that it may help others.

Re: Important Issue

mbenbow — Fri, 11 Aug 2006 13:49:38 GMT

Hey,

Microsoft made a major change in functionality in MS Access and associated DLLs from Access 97 to Access 2000 - 2003. When installing InfoPath 2003, it would "upgrade" these DLLs that affect MS Access.

The major change I have noticed from working with Access databases is that in code when you declare the following:
Dim db as Database

Access 97 automitically assumes that you were referring to DAO. Access 2000 and above automatically assumes you are referring to ADO.

What I had to do to "fix" the issue with access database applications was to clarify the code as follows and ensure that the reference for the database code was using DAO 3.x library.

Try changing your code to:
Dim db as DAO.Database
Dim rec as DAO.Recordset
Dim qdf as DAO.QueryDef
etc....

Not sure if this will fix your problem, but it has been a known issue for all Access programmers since Access 2000.

MB

Re: Important Issue

Matt Faus — Fri, 11 Aug 2006 13:31:13 GMT

This is an interesting situation, but I very seriously doubt that the installation of InfoPath would do any kind of alteration of existing code libraries.

It might have upgraded them, and if you are using functions that have been deprecated, this would cause a problem, but I just don't believe that this would happen. If you have the source code for the program, you should try compiling it on a machine that has InfoPath installed and look at all the warnings that the compiler throws - this will tell you where the deprecated functions are being called if thare are any.

A more likely scenario was that maybe InfoPath took control of default file handlers. Does this DOE program use XML technology at all?

Important Issue

nukkumatti — Fri, 11 Aug 2006 11:41:01 GMT

Hi all,

I have my doubts that someone can help me/us here but at the moment I wouldn't know any better place to ask.

In my company there appeared a serious problem after installing InfoPath on some machines. To be exact on machines which use DOE.
DOE stands for Distributed Order Entry and it is a customized application within our company running on Access97 Runtime (ATD97) or MsAccess97 Full version. Our guess is that the installation of InfoPath modified a collection of functions or components (e.g VBA library / MDAC / DAO ...) that the application was using. What ever the DOE application doesn't not work anymore and we are sure that it has something to do wiht the installtion of InfoPath.

So if someone had a similar experience already or has some idea what could have caused the trouble please let me know.

Thx to all in advance