Re: Database connection problem on VB6.0

Jim Carlock wrote:
Jim Carlock wrote:
"Engada" pondered...
: I have an application written in VB6.0 which has previously
: been interfacing with MS SQL server 2000, which I have
: moved to Postgres 8.2.3.
:
: When attempting to create an ODBC workspace, the app now
: errors on the following line of code:
:
: Set autodrs_work = CreateWorkspace("autodrs", _
: g_strUserName, _
: g_strPWD, _
: dbUseODBC)
:
: Where g_str* variables are globals holding the username and
: password for connecting to the db.
:
: The following is the resulting error:
: 3633 Cannot load DLL: '?????L?'

"Engada" posted...
: I'm using Microsot DAO 3.6 Object Library.
:
: Variable declaration:

Try changing those to:

Private autodrs_work As DAO.Workspace
Private autodrs_db As DAO.Database

I don't have a copy of Postgres installed. Are you limited to
Postgres?

One option might be to try getting an Access .mdb to link to
the Postgres through your ODBC connection. The ODBC
connection should be visible through the Link wizard. Just
right click inside the white window area in an Access file
and then click on Link tables...

If Access can create a link, then we know your ODBC is
configured properly and ready to go. This should provide
a little help here.


No dice, still getting the same error.

The line that gives the error I made the same change to, i.e:
DBEngine.DefaultType = DAO.dbUseODBC

But still complaining about error 3633.

Regards,
Paul.

--
Posted via a free Usenet account from http://www.teranews.com

.

Relevant Pages

  • Re: Database connection problem on VB6.0
    ... Jim Carlock wrote: ... I don't have a copy of Postgres installed. ... the Postgres through your ODBC connection. ... connection should be visible through the Link wizard. ...
    (microsoft.public.vb.general.discussion)
  • Re: Database connection problem on VB6.0
    ... I have nothing major against SQL Server, this was purely a financial decision. ... Postgres appears to me to be the most functional, stable, robust etc rdbms out there - right up there with oracle and sql server in those areas. ... the Postgres through your ODBC connection. ... connection should be visible through the Link wizard. ...
    (microsoft.public.vb.general.discussion)
  • Re: VFP Updates?
    ... Try talking ODBC or OleDb and they say HU. ... make up my apps so that what ever they want to run has to be from a command ... kind of connection and assign it the right to do exactly what you want. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: MS Access looks for .mdb rather than Progress schema
    ... # Same query previously worked in Progress 8.x using SQL89. ... This entry allows you to keep your existing code written with the ODBC ... BTW, if you put all of the connect information into the connect string, ... I also tried putting the whole thing in the connection string: ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access and processor usage
    ... and you are using an ODBC connection, that would be your bottle neck. ... bottleneck - need to step up to Sql Server. ...
    (comp.databases.ms-access)