Trouble running VB 3.0 Database App in NT

Trouble running VB 3.0 Database App in NT

Post by Dan Sta » Fri, 10 Jul 1998 04:00:00



Hi,

I have a VB 3.0 database application that runs fine in
Windows 95.  However, when I try to run it on NT 4.0 (or
3.51 for that matter), the ODBC dialog pops up when the code
tries to open the Access database which is being accessed
via the JET engine, not ODBC.  I can not figure out why it
is doing this.  If anyone can offer a hand, please do.

Regards,

Dan

  vcard.vcf
< 1K Download
 
 
 

Trouble running VB 3.0 Database App in NT

Post by Glenn Miyashi » Sat, 11 Jul 1998 04:00:00


The ODBC dialog pops up when you perform an OpenDatabase with an empty path to the
.MDB. Perhaps you are expecting a variable to have a valid path and it isnt?

>Hi,
>I have a VB 3.0 database application that runs fine in
>Windows 95.  However, when I try to run it on NT 4.0 (or
>3.51 for that matter), the ODBC dialog pops up when the code
>tries to open the Access database which is being accessed
>via the JET engine, not ODBC.  I can not figure out why it
>is doing this.  If anyone can offer a hand, please do.
>Regards,
>Dan
>--------------A11F355EFC52ADD8D98ED7B6
>Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
>Content-Transfer-Encoding: 7bit
>Content-Description: Card for Dan Star
>Content-Disposition: attachment; filename="vcard.vcf"
>begin:          vcard
>fn:             Dan Star
>n:              Star;Dan

>x-mozilla-cpt:  ;0
>x-mozilla-html: TRUE
>version:        2.1
>end:            vcard
>--------------A11F355EFC52ADD8D98ED7B6--

***********************
Why am I riding in this Hand Basket and just where are we going?

Email: use glennmiy AT inreach DOT com

 
 
 

Trouble running VB 3.0 Database App in NT

Post by Dan Sta » Mon, 13 Jul 1998 04:00:00


I thought that I verified that I had a valid path.  Though I
do not think this is the problem I will check again.

Dan



> The ODBC dialog pops up when you perform an OpenDatabase with an empty path to the
> .MDB. Perhaps you are expecting a variable to have a valid path and it isnt?

> >Hi,

> >I have a VB 3.0 database application that runs fine in
> >Windows 95.  However, when I try to run it on NT 4.0 (or
> >3.51 for that matter), the ODBC dialog pops up when the code
> >tries to open the Access database which is being accessed
> >via the JET engine, not ODBC.  I can not figure out why it
> >is doing this.  If anyone can offer a hand, please do.

> >Regards,

> >Dan
> >--------------A11F355EFC52ADD8D98ED7B6
> >Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
> >Content-Transfer-Encoding: 7bit
> >Content-Description: Card for Dan Star
> >Content-Disposition: attachment; filename="vcard.vcf"

> >begin:          vcard
> >fn:             Dan Star
> >n:              Star;Dan

> >x-mozilla-cpt:  ;0
> >x-mozilla-html: TRUE
> >version:        2.1
> >end:            vcard

> >--------------A11F355EFC52ADD8D98ED7B6--

> ***********************
> Why am I riding in this Hand Basket and just where are we going?

> Email: use glennmiy AT inreach DOT com

  vcard.vcf
< 1K Download
 
 
 

Trouble running VB 3.0 Database App in NT

Post by Barr » Tue, 14 Jul 1998 04:00:00





>The ODBC dialog pops up when you perform an OpenDatabase with an empty path to the
>.MDB. Perhaps you are expecting a variable to have a valid path and it isnt?

>>Hi,

>>I have a VB 3.0 database application that runs fine in
>>Windows 95.  However, when I try to run it on NT 4.0 (or
>>3.51 for that matter), the ODBC dialog pops up when the code
>>tries to open the Access database which is being accessed
>>via the JET engine, not ODBC.  I can not figure out why it
>>is doing this.  If anyone can offer a hand, please do.

>>Regards,

>>Dan
>>--------------A11F355EFC52ADD8D98ED7B6
>>Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
>>Content-Transfer-Encoding: 7bit
>>Content-Description: Card for Dan Star
>>Content-Disposition: attachment; filename="vcard.vcf"

>>begin:          vcard
>>fn:             Dan Star
>>n:              Star;Dan

>>x-mozilla-cpt:  ;0
>>x-mozilla-html: TRUE
>>version:        2.1
>>end:            vcard

>>--------------A11F355EFC52ADD8D98ED7B6--

>***********************
>Why am I riding in this Hand Basket and just where are we going?

>Email: use glennmiy AT inreach DOT com

Many apps will ask for a password under WinNT that they don't need (or
ask for) under Win95.  I'd look at this first.

HTH,

Barry
eggers1 AT tsil DOT net

 
 
 

Trouble running VB 3.0 Database App in NT

Post by Liam » Tue, 14 Jul 1998 04:00:00


What version(s) of DAO do you have installed on the NT PC?
What version of MS Access is the database in?

Does DAO try to open old versions of MS Access dbs through ODBC drivers?

Hope this helps...

Liam


>Hi,

>I have a VB 3.0 database application that runs fine in
>Windows 95.  However, when I try to run it on NT 4.0 (or
>3.51 for that matter), the ODBC dialog pops up when the code
>tries to open the Access database which is being accessed
>via the JET engine, not ODBC.  I can not figure out why it
>is doing this.  If anyone can offer a hand, please do.

>Regards,

>Dan

 
 
 

1. Trouble Porting VB 3.0 SQLServer App to VB 4.0 and Oracle

We are in the process of moving our application from VB 3.0 and SQLServer 4.2 to VB 4.0 and Oracle 7.2.  We
are having trouble connecting to our Oracle database via ODBC.  We have configured the datasource using the
32-bit ODBC setup tool, and we have SQL*Net 2.2 installed.  We are able to connect to this datasource using MS
Query 32-bit version and through Crystal Reports.  But we are unable to connect to the database using the VB
4.0 version of our application.  We are using the same datasource as the two other programs mentioned.  We are
getting a "3146 ODBC Call failed" error when trying to execute the first SQL statement after our database
connect.  I'm not sure if the database connect statement is even successful.  Any insight would be
appreciated.

thanks - Brent

2. DALLAS -- ORACLE Finanicals or HR

3. Running a VB App with dataenvironment under NT

4. Sybase SQL grammar?

5. Running VB app as NT Service

6. Log Transaction Tool

7. VB app won't run on NT Server

8. Update to LDAP via ADO?

9. Running VB app from AT Scheduler on NT Workstation

10. Converting VB 3.0 app to VB 4.0

11. MFC App Wizard-generated database application runs like a dog under NT 4.0

12. Trouble running SQL App over 128kb/s connection

13. Trouble running SQL App over ISDN and 512kb line