Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Problem Opening Access Programatically

  • Please log in to reply
2 replies to this topic

#1 budasbli


  • Members
  • 1 posts
  • Local time:06:13 AM

Posted 30 April 2007 - 08:28 AM


My application is distibuted to users who may be running any version of MSOffice 97 or above. My development machine runs 97 as the 'lowest common denominator'. My VB5 application populates tables in an Access database then opens the database to run a predefined Access report. I have 2 problems. 1) whenever I issue a new reports database to someone using later that MS Office 97 the program won't open the database unles it has been 'manually' opened (without converting it) first via Access. This is annoying more than anything else but problem 2) is that sometimes Access gives the messag to the effect that it has automatically converted the VB5 code in the database - don't know what code this could be - at which point my application won't open it at all - no error message either.

Help please?

BC AdBot (Login to Remove)


#2 groovicus


  • Security Colleague
  • 9,963 posts
  • Gender:Male
  • Location:Centerville, SD
  • Local time:12:13 AM

Posted 30 April 2007 - 11:17 AM

As far as problem 2, databases can use stored procedures, but those procedures are not in VB, at least as far as I know. Perhaps they are (written in VB) for Access? SQL uses , well, SQL syntax to create procedures. Of course, that is an assumption based on your interpretation of the error message. I can't think of any other reason for an error like that.

#3 Keithuk


  • Members
  • 960 posts
  • Gender:Male
  • Local time:07:13 AM

Posted 01 May 2007 - 04:34 PM

It sounds like your problem is your references to the database. If you are using Office 97 then depending on what you are using to access this database, ADO, DAO or Adodc? You will need to reference Microsoft DAO 3.51 Object Library (Dao350.dll) or Microsoft ActiveX Data Objects 2.5 Library (msado25.tlb).

There should be any need to convert the database. Providing these files are included in your installation package I don't see a problem. :thumbsup:


Windows ME (spare computer)
Windows XP 2002 Professional SP3 (desktop computer)
Windows 7 Professional SP1 32bit (laptop computer)

Windows 8 64bit spare drive for laptop computer

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users