By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,854 Members | 2,004 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,854 IT Pros & Developers. It's quick & easy.

VB and an Access 2003

P: n/a
I'm using VB and an Access 2003. The db was originally created in
Access 2000, but the computer had to have things reinstalled and now
has Access 2003.

So I was wondering if there are any compatibility issues using the two
programs. I know that when using data controls you can select Access
2000 for the connect property. This VB program also uses DAO and not
ADO.

I've been having some weird things happen to the program since using
Access 2003 and am debating uninstalling Access 2003 and reinstalling
Access 2000.

Any ideas what I should do?

Jun 30 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Ecohouse" <vi*******@netzero.com> wrote in
news:11**********************@h44g2000cwa.googlegr oups.com:
I'm using VB and an Access 2003. The db was originally created in
Access 2000, but the computer had to have things reinstalled and
now has Access 2003.

So I was wondering if there are any compatibility issues using the
two programs. I know that when using data controls you can select
Access 2000 for the connect property. This VB program also uses
DAO and not ADO.

I've been having some weird things happen to the program since
using Access 2003 and am debating uninstalling Access 2003 and
reinstalling Access 2000.

Any ideas what I should do?


What does VB have to do with Access 2003? Or Access 2000?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jun 30 '06 #2

P: n/a
On Fri, 30 Jun 2006 15:47:12 -0500, "David W. Fenton" <XX*******@dfenton.com.invalid> wrote:
"Ecohouse" <vi*******@netzero.com> wrote in
news:11**********************@h44g2000cwa.googleg roups.com:
I'm using VB and an Access 2003. The db was originally created in
Access 2000, but the computer had to have things reinstalled and
now has Access 2003.

So I was wondering if there are any compatibility issues using the
two programs. I know that when using data controls you can select
Access 2000 for the connect property. This VB program also uses
DAO and not ADO.

I've been having some weird things happen to the program since
using Access 2003 and am debating uninstalling Access 2003 and
reinstalling Access 2000.

Any ideas what I should do?


What does VB have to do with Access 2003? Or Access 2000?


I assume he is using VB6 with connection by JET to an MDB file.
Jul 1 '06 #3

P: n/a
polite person <sn**@snippers.comwrote in
news:e9********************************@4ax.com:
On Fri, 30 Jun 2006 15:47:12 -0500, "David W. Fenton"
<XX*******@dfenton.com.invalidwrote:
>>"Ecohouse" <vi*******@netzero.comwrote in
news:11**********************@h44g2000cwa.google groups.com:
>>I'm using VB and an Access 2003. The db was originally created
in Access 2000, but the computer had to have things reinstalled
and now has Access 2003.

So I was wondering if there are any compatibility issues using
the two programs. I know that when using data controls you can
select Access 2000 for the connect property. This VB program
also uses DAO and not ADO.

I've been having some weird things happen to the program since
using Access 2003 and am debating uninstalling Access 2003 and
reinstalling Access 2000.

Any ideas what I should do?

What does VB have to do with Access 2003? Or Access 2000?

I assume he is using VB6 with connection by JET to an MDB file.
So, what does his post have to do with ACCESS?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 1 '06 #4

P: n/a
"David W. Fenton" wrote
So, what does his post have to do with ACCESS?
Where would you expect a VB user to post, given that even Microsoft calls a
Jet database "an Access database", as do many (all?) of us here, from time
to time, even though we know better, If I recall correctly, the
comp.lang.basic.visual.databases newsgroup has long since dried up due to
lack of interest (most people never posted to any of the "new" newsgroups
that were officially created from c.l.b.v, but only to the c.l.b.v.misc,
which they regarded as the "successor" to c.l.b.v).

I believe that Microsoft called it an "Access database" in documentation for
the Visual Basic products, too. So, it seems to me to be a forgiveable
mispost.

Larry
Jul 2 '06 #5

P: n/a
Both programs use the same database engine and the
same database format and the same DAO objects.

If you look in the VB project file, you will see a
DAO reference. The same DAO reference used by
Access 2000 and Access 2003.

It is extremely unlikely that your VB project has
a reference to either Access 2000 or Access 2003.

Data controls can use either the database format
and engine used by Access 2000/2003, or the database
format and engine used by Access 97.

(david)
"Ecohouse" <vi*******@netzero.comwrote in message
news:11**********************@h44g2000cwa.googlegr oups.com...
I'm using VB and an Access 2003. The db was originally created in
Access 2000, but the computer had to have things reinstalled and now
has Access 2003.

So I was wondering if there are any compatibility issues using the two
programs. I know that when using data controls you can select Access
2000 for the connect property. This VB program also uses DAO and not
ADO.

I've been having some weird things happen to the program since using
Access 2003 and am debating uninstalling Access 2003 and reinstalling
Access 2000.

Any ideas what I should do?

Jul 2 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.