Local DB Affected By VPN

I work on a local copy of a database (Access 2000 MDB with ODBC linked
tables to a SQL 7 database). The SQL Server db I'm working with is on my C
drive (MSDE). Occasionally I'll connect to a VPN to do something on a remote
computer, using PC Anywhere to perform the task. Doesn't involve my front or
back end at all, except that the computer I'm VPNing to has a SQL database
running.

OK, so I'm using my db; I connect to the VPN, and do my thing. Everything's
fine. However, if I then disconnect from the VPN (or if the VPN connection
times out and disconnects itself), I then can no longer access my local SQL
Server database. My Access application still works fine, as long as it
doesn't have to look at any data. When it does have to look at data, I get
ODBC call failed. I have to close and reopen my Access database, and then
everything is fine.

So, it seems that, for some reason, when I connect to the VPN, my local SQL
Server or the ODBC driver or something in the mix is looking at that remote
database as part of what I'm using. Then, when the VPN connection is closed,
it won't access my local database for some reason.

Oh, and my local database and the remote database both have the same name.
So that may be part of the problem.

Any ideas as to what's going on?

Thanks!

Neil

Re: Local DB Affected By VPN

On 26 Nov, 10:15, "Neil" wrote:
> I work on a local copy of a database (Access 2000 MDB with ODBC linked
> tables to a SQL 7 database). The SQL Server db I'm working with is on my C
> drive (MSDE). Occasionally I'll connect to a VPN to do something on a remote
> computer, using PC Anywhere to perform the task. Doesn't involve my front or
> back end at all, except that the computer I'm VPNing to has a SQL database
> running.
>
> OK, so I'm using my db; I connect to the VPN, and do my thing. Everything's
> fine. However, if I then disconnect from the VPN (or if the VPN connection
> times out and disconnects itself), I then can no longer access my local SQL
> Server database. My Access application still works fine, as long as it
> doesn't have to look at any data. When it does have to look at data, I get
> ODBC call failed. I have to close and reopen my Access database, and then
> everything is fine.
>
> So, it seems that, for some reason, when I connect to the VPN, my local SQL
> Server or the ODBC driver or something in the mix is looking at that remote
> database as part of what I'm using. Then, when the VPN connection is closed,
> it won't access my local database for some reason.
>
> Oh, and my local database and the remote database both have the same name.
> So that may be part of the problem.
>
> Any ideas as to what's going on?
>
> Thanks!
>
> Neil

It's only a guess but have you got the means of using Remote Desktop
Terminal Services Client or MSN Messenger Remote Assistance (As a
test) instead of PCAnywhere? I worked on the Laplink support line many
years ago and can imagine that this might be the issue and rings some
bells but things have changed since.

All the best,

Martin

Re: Local DB Affected By VPN

On 27 Nov, 13:46, theintrepidfox wrote:
> On 26 Nov, 10:15, "Neil" wrote:
>
>
>
>
>
> > I work on a local copy of a database (Access 2000 MDB with ODBC linked
> > tables to a SQL 7 database). The SQL Server db I'm working with is on my C
> > drive (MSDE). Occasionally I'll connect to a VPN to do something on a remote
> > computer, using PC Anywhere to perform the task. Doesn't involve my front or
> > back end at all, except that the computer I'm VPNing to has a SQL database
> > running.
>
> > OK, so I'm using my db; I connect to the VPN, and do my thing. Everything's
> > fine. However, if I then disconnect from the VPN (or if the VPN connection
> > times out and disconnects itself), I then can no longer access my local SQL
> > Server database. My Access application still works fine, as long as it
> > doesn't have to look at any data. When it does have to look at data, I get
> > ODBC call failed. I have to close and reopen my Access database, and then
> > everything is fine.
>
> > So, it seems that, for some reason, when I connect to the VPN, my local SQL
> > Server or the ODBC driver or something in the mix is looking at that remote
> > database as part of what I'm using. Then, when the VPN connection is closed,
> > it won't access my local database for some reason.
>
> > Oh, and my local database and the remote database both have the same name.
> > So that may be part of the problem.
>
> > Any ideas as to what's going on?
>
> > Thanks!
>
> > Neil
>
> It's only a guess but have you got the means of using Remote Desktop
> Terminal Services Client or MSN Messenger Remote Assistance (As a
> test) instead of PCAnywhere? I worked on the Laplink support line many
> years ago and can imagine that this might be the issue and rings some
> bells but things have changed since.
>
> All the best,
>
> Martin- Hide quoted text -
>
> - Show quoted text -

The reason why I'm suggestin it is because PCAnywhere is perhaps
trying to synchromize files between the client and host (including
your .mdb) which is maybe still and remains in use by the Sync Process
when the VPN times out or disconnects.

Re: Local DB Affected By VPN

Actually, it usually happens after PCAnywhere has been closed. While
PCAnywhere is open, the VPN connection stays active. After I close
PCAnywhere, if I don't disconnect from the VPN, then eventually the VPN
connection times out.

So, a typical scenario is: open Access app connected to local SQL Server;
later, connect to VPN and do stuff via PCAnywhere; close PCAnywhere; later,
VPN connection disconnects, and then connection to local SQL Server fails.
Have to close and reopen MDB for it to work.

Strange....


"theintrepidfox" wrote in message
news:3e278590-302d-4549-82d4-2e12c0b51b1a@i29g2000prf.google groups.com...
> On 26 Nov, 10:15, "Neil" wrote:
>> I work on a local copy of a database (Access 2000 MDB with ODBC linked
>> tables to a SQL 7 database). The SQL Server db I'm working with is on my
>> C
>> drive (MSDE). Occasionally I'll connect to a VPN to do something on a
>> remote
>> computer, using PC Anywhere to perform the task. Doesn't involve my front
>> or
>> back end at all, except that the computer I'm VPNing to has a SQL
>> database
>> running.
>>
>> OK, so I'm using my db; I connect to the VPN, and do my thing.
>> Everything's
>> fine. However, if I then disconnect from the VPN (or if the VPN
>> connection
>> times out and disconnects itself), I then can no longer access my local
>> SQL
>> Server database. My Access application still works fine, as long as it
>> doesn't have to look at any data. When it does have to look at data, I
>> get
>> ODBC call failed. I have to close and reopen my Access database, and then
>> everything is fine.
>>
>> So, it seems that, for some reason, when I connect to the VPN, my local
>> SQL
>> Server or the ODBC driver or something in the mix is looking at that
>> remote
>> database as part of what I'm using. Then, when the VPN connection is
>> closed,
>> it won't access my local database for some reason.
>>
>> Oh, and my local database and the remote database both have the same
>> name.
>> So that may be part of the problem.
>>
>> Any ideas as to what's going on?
>>
>> Thanks!
>>
>> Neil
>
> It's only a guess but have you got the means of using Remote Desktop
> Terminal Services Client or MSN Messenger Remote Assistance (As a
> test) instead of PCAnywhere? I worked on the Laplink support line many
> years ago and can imagine that this might be the issue and rings some
> bells but things have changed since.
>
> All the best,
>
> Martin

Re: Local DB Affected By VPN

"theintrepidfox" wrote in message
news:9cb60b5b-5160-4afe-8555-8ed2bed12b09@s36g2000prg.google groups.com...
> On 27 Nov, 13:46, theintrepidfox wrote:
>> On 26 Nov, 10:15, "Neil" wrote:
>>
>>
>>
>>
>>
>> > I work on a local copy of a database (Access 2000 MDB with ODBC linked
>> > tables to a SQL 7 database). The SQL Server db I'm working with is on
>> > my C
>> > drive (MSDE). Occasionally I'll connect to a VPN to do something on a
>> > remote
>> > computer, using PC Anywhere to perform the task. Doesn't involve my
>> > front or
>> > back end at all, except that the computer I'm VPNing to has a SQL
>> > database
>> > running.
>>
>> > OK, so I'm using my db; I connect to the VPN, and do my thing.
>> > Everything's
>> > fine. However, if I then disconnect from the VPN (or if the VPN
>> > connection
>> > times out and disconnects itself), I then can no longer access my local
>> > SQL
>> > Server database. My Access application still works fine, as long as it
>> > doesn't have to look at any data. When it does have to look at data, I
>> > get
>> > ODBC call failed. I have to close and reopen my Access database, and
>> > then
>> > everything is fine.
>>
>> > So, it seems that, for some reason, when I connect to the VPN, my local
>> > SQL
>> > Server or the ODBC driver or something in the mix is looking at that
>> > remote
>> > database as part of what I'm using. Then, when the VPN connection is
>> > closed,
>> > it won't access my local database for some reason.
>>
>> > Oh, and my local database and the remote database both have the same
>> > name.
>> > So that may be part of the problem.
>>
>> > Any ideas as to what's going on?
>>
>> > Thanks!
>>
>> > Neil
>>
>> It's only a guess but have you got the means of using Remote Desktop
>> Terminal Services Client or MSN Messenger Remote Assistance (As a
>> test) instead of PCAnywhere? I worked on the Laplink support line many
>> years ago and can imagine that this might be the issue and rings some
>> bells but things have changed since.
>>
>> All the best,
>>
>> Martin- Hide quoted text -
>>
>> - Show quoted text -
>
> The reason why I'm suggestin it is because PCAnywhere is perhaps
> trying to synchromize files between the client and host (including
> your .mdb) which is maybe still and remains in use by the Sync Process
> when the VPN times out or disconnects.

Yeah, I don't think that's it. I tried connecting to the VPN without doing
anything else, and the results were the same. Something in SQL Server itself
is looking at that other server for some reason. Maybe because they both
have same-named databases. I don't know.

Thanks,

Neil