Error opening an ODBC connection

[ticron]

Hi.

I'm getting an error message in ACCESS when I try to open a MDB:

"Then system has encountered an error opening an ODBC connection."

I open this file once per month and its worked for 2 yrs. I can see the file I want to open on the network drive, I simply cannot open it The IP address for the file server was just changed recently so I reckon thats the problem? I don't know how to change the setting. Can anyone tell me how to fix it?

Thank you

T.

 

[psemianonymous]

The easiest way to deal with these sort of problems is to try and re-create the ODBC link using either the ODBC manager or the table linking wizard (depending on how you're using the ODBC connection--as an Access table, or in a direct connection from a recordset?).

Without a lot more details there's no better answer for you.

 

[assets]

ticron,

I had a similar problem.
When I went through and ticked all the ODBC. The problem was fixed.

 

[ticron]

Hi thx for the replies.

"depending on how you're using the ODBC connection--as an Access table, or in a direct connection from a recordset?"

I don't know

The accounting software makes a .mdb file and I open it w/ access to print month end reports.

"When I went through and ticked all the ODBC."

I don't know what that means. The only reason I am so called "network admin" is b/c I'm better at Quake than anyone else here. I don't know anything about ODBC.

I'd better call MS b/c if I make a mistake and flub something bad I won't be very popular here at work

Thx again for the replies. Take care.

T.

 

[ticron]

I've discovered its a pervasive issue.

"The Connection Manager is not running on the specified port"

I can't get it to run. If anyone has any more ideas I'm all ears/eyes

Thank you

 

[psemianonymous]

Call your help desk or find whoever made the program. This is your best bet.

 

[ticron]

Hey foolio, for some reason pervasive is trying to find the server at 192.168.1.90. Thats not the IP anymore, its been changed. I edited all the hosts files making sure they point to the right number, and I can ping the server by name or IP from the client.

For whatever reason Pervasive just insists the server is still at the .90 address. >_< darnit ! Any idea how I can point Pervasive to the right addy?

Thx

T.

 

[psemianonymous]

If you find a forum for 'Pervasive' or whatever program you're running, you'll find better help than asking people like me. I've never even heard of the program before.

So I basically give up, because neither you nor I have any idea how the ODBC connection is set up, or how to change it.

So ask someone who knows.

 

[ticron]

Yes the problem seems to have evolved from access issue to a Pervasive issue Sry for spamming your BBS w/ my dumb questions ;P

thx for the help. take care.

T.

 

[assets]

Ticron,

no question is dumb. People ask because they do not know and use forums to tyy and fin other who may have similar problem ar know the answer. I have imbeded code for drives (on networks) in my databases but not ports.