Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old October 1st, 2003, 12:56 PM
Authorized User
Join Date: Sep 2003
Posts: 35
Thanks: 0
Thanked 0 Times in 0 Posts

Hey bob,
thnx for all that! I figured that they were seperate issues after looking up some things. I do have all the libraries refereced as you said. I have office 9.0 lib instaleld so im using that. Everything works fine in access 97 but in access 2000 i keep getting problems with the custom commandbar. It does compile but doesnt run when you open a form. And I have access 97 and access 2000 installed. I didnt know that could give me a problem, does it???


quote:Originally posted by Bob Bedell

there should only be one version (the latest) of this particular library listed in your references dialog
Unless of course you have multiple versions of Access installed.

Old October 2nd, 2003, 12:32 PM
Authorized User
Join Date: Sep 2003
Posts: 35
Thanks: 0
Thanked 0 Times in 0 Posts


I figured out my problem. The person who designed the access 97 database created a custom menu bar which was not converted correctly so for the commandbar's to work i recreated the menu bar in access 2000. Thanks Bob for all the help.

I have an issue converting DAO to ADO though, if anyone can help? how does DAO's workspace convertions look like in ADO???


Sam Gharnagh
Jr. Programmer Analyst
Comp Sci at UofW
Old October 2nd, 2003, 02:54 PM
Friend of Wrox
Join Date: Jun 2003
Posts: 1,093
Thanks: 1
Thanked 12 Times in 11 Posts

Hi Sam,

Glad to here you got it going.

In ADO the Connection object does double duty compared to DAO.

In DAO the Workspace object defines the session for a user and the Database object defines a data source.

In ADO the Connection object does both. It defines a session for a user for a data source. The conversion looks like:

Dim dbs as DAO.Database
Set dbs = DBEngine.Workspaces(0).OpenDatabase(".\Northwind")

Dim cnn as New ADO.Connection
cnn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=.\Northwind.mdb;"

(though there are several ways to write these statments)



Similar Threads
Thread Thread Starter Forum Replies Last Post
migrating from access to SQL morphy VB Databases Basics 1 December 10th, 2004 04:12 PM
Coverting from Access 2000 to 97 timmaher Access 1 August 18th, 2004 08:47 AM
Select the correct version of Access 97/2000 setyna VB Databases Basics 2 August 16th, 2004 03:54 AM
Access 2000 to Access 97 happygv Access 5 April 23rd, 2004 10:06 AM
ADE file in Access 2000 <---> Access XP ginoitalo Access 3 April 14th, 2004 09:06 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.