[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 696
  • Last Modified:

DAO 3.6 - is it compatible with Windows 2003 Server?

My application installs and works correctly on the following platforms Win98, WinXP, Win2000, but does NOT work on Win2003?  There are no install errors in Win2003, but I get a OLE DB error as soon as I run my application (PowerCombo).  I distribute DAO3.6 and Win2003 has MDAC 2.8 already installed on it, so I'm confused as to why my app will NOT run on Win2003.

The specific error is:

PowerCombo Database error : OLE DB Error (0X8007007F)

I've check all the dependancy files for PowerCombo as well as DAO 3.6 and all seem to be there.

Any suggestions?

Thanks, Rob.
0
RobAinscough
Asked:
RobAinscough
  • 6
  • 3
1 Solution
 
Anthony PerkinsCommented:
Just be aware that MDAC 2.8 does not contain any JET components.
0
 
Anthony PerkinsCommented:
Also, are you sure you are using DAO through out your app, the OLE DB error points to the use of ADO, not DAO.
0
 
pique_techCommented:
I see what acperkins is saying:  have you explicitly DIMmed everything that's relevant as DAO.Xxxxxx where Xxxxxx is the name of some DAO object?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
RobAinscoughAuthor Commented:
Yes I'm sure.  Re-read my original post, we have tested my application install (using InstallShield 10.0) on 3 "virgin" state operating systems, Win98, WinXP, Win2000 and the application works like a champ and does NOT have any errors.  Come to install it on Win2003 and then run my application, I get the error.  So clearly is it not a coding issue, but something unique about Win2003.

We tried installing just the Jet 4.0 (sp8) component for Win2003, but that didn't resolve the issue.

Has anyone successfully run a VB6 application using only DAO 3.6 on a Win2003 OS?

Thanks, Rob.
0
 
Anthony PerkinsCommented:
>>So clearly is it not a coding issue, but something unique about Win2003.<<
I am afraid it is.  You will come to terms with it in the end.

Good luck.
0
 
RobAinscoughAuthor Commented:
Not sure what you mean by "I am afraid it is."?

I resolved the problem, apparently it is a compatibility issue with SQL 2000 Server (which was also installed on the same Win2003 server machine).  I re-installed Win2003 from scratch and didn't put SQL 2000 Server on it, and viola, my application is working consistantly and correctly now.

Rob.
0
 
Anthony PerkinsCommented:
Then please close this question.  Here's how:
I answered my question myself. What do I do?
http://www.experts-exchange.com/Programming/Programming_Languages/Visual_Basic/VB_Databases/help.jsp#hi70
0
 
RobAinscoughAuthor Commented:
And I pay for this abuse -- geez, chill out.
0
 
Anthony PerkinsCommented:
Feel free to post a message in Community Support if you feel my comments were in any way inappropriate.  Make sure to include a reference to this thread.
0
 
Anthony PerkinsCommented:
No problem.  Fine with me.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now