location of ODBC drivers for SQL 2k5 x64 in Win Server 2003 x64 ST

Hi,
I've got Win Server 2003 Standard 64bit edition trying to work with SQL 2005
standard 64bit edition however there is a problem.
I need to locate the ODBC driver in Win Ser.
I know where they are in the 32bit edition but not in the 64bit version.
can anyone help?
Thanks
Olgun.Ucurel@.ccsmedia.comIs there a 64 bit ODBC Driver? I didnt think that there was. You might have
to compile your application in x86 or if you are using SSIS or DTS exec you
can use this post...
http://forums.microsoft.com/MSDN/Sh...603814&SiteID=1
Can you use the OLE DB Driver?
C:\WINDOWS\SysWOW64\odbcad32.exe
uses...
odbc32.dll
and
C:\WINDOWS\System32\odbcad32.exe
uses
odbc32.dll
I am sure others will have some thoughts as well.
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Olgun" <Olgun@.discussions.microsoft.com> wrote in message
news:9BA59FAC-D013-4BF4-9700-A97D71D65545@.microsoft.com...
> Hi,
> I've got Win Server 2003 Standard 64bit edition trying to work with SQL
> 2005
> standard 64bit edition however there is a problem.
> I need to locate the ODBC driver in Win Ser.
> I know where they are in the 32bit edition but not in the 64bit version.
> can anyone help?
> Thanks
> Olgun.Ucurel@.ccsmedia.com|||Olgun wrote:
> Hi,
> I've got Win Server 2003 Standard 64bit edition trying to work with SQL 20
05
> standard 64bit edition however there is a problem.
> I need to locate the ODBC driver in Win Ser.
> I know where they are in the 32bit edition but not in the 64bit version.
> can anyone help?
> Thanks
> Olgun.Ucurel@.ccsmedia.com
As far as I know the ODBC driver is not working on 64 bits Windows. You
could use OLEDB instead, which is working fine.
Regards,
lucm

location of ODBC drivers for SQL 2k5 x64 in Win Server 2003 x64 ST

Hi,
I've got Win Server 2003 Standard 64bit edition trying to work with SQL 2005
standard 64bit edition however there is a problem.
I need to locate the ODBC driver in Win Ser.
I know where they are in the 32bit edition but not in the 64bit version.
can anyone help?
Thanks
Olgun.Ucurel@.ccsmedia.com
Is there a 64 bit ODBC Driver? I didnt think that there was. You might have
to compile your application in x86 or if you are using SSIS or DTS exec you
can use this post...
http://forums.microsoft.com/MSDN/Sho...03814&SiteID=1
Can you use the OLE DB Driver?
C:\WINDOWS\SysWOW64\odbcad32.exe
uses...
odbc32.dll
and
C:\WINDOWS\System32\odbcad32.exe
uses
odbc32.dll
I am sure others will have some thoughts as well.
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Olgun" <Olgun@.discussions.microsoft.com> wrote in message
news:9BA59FAC-D013-4BF4-9700-A97D71D65545@.microsoft.com...
> Hi,
> I've got Win Server 2003 Standard 64bit edition trying to work with SQL
> 2005
> standard 64bit edition however there is a problem.
> I need to locate the ODBC driver in Win Ser.
> I know where they are in the 32bit edition but not in the 64bit version.
> can anyone help?
> Thanks
> Olgun.Ucurel@.ccsmedia.com
|||Olgun wrote:
> Hi,
> I've got Win Server 2003 Standard 64bit edition trying to work with SQL 2005
> standard 64bit edition however there is a problem.
> I need to locate the ODBC driver in Win Ser.
> I know where they are in the 32bit edition but not in the 64bit version.
> can anyone help?
> Thanks
> Olgun.Ucurel@.ccsmedia.com
As far as I know the ODBC driver is not working on 64 bits Windows. You
could use OLEDB instead, which is working fine.
Regards,
lucm

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
On 26 Nov, 10:15, "Neil" <nos...@.nospam.net> 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
|||On 27 Nov, 13:46, theintrepidfox <theintrepid...@.hotmail.com> wrote:
> On 26 Nov, 10:15, "Neil" <nos...@.nospam.net> wrote:
>
>
>
>
>
>
> 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.
|||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" <theintrepidfox@.hotmail.com> wrote in message
news:3e278590-302d-4549-82d4-2e12c0b51b1a@.i29g2000prf.googlegroups.com...
> On 26 Nov, 10:15, "Neil" <nos...@.nospam.net> wrote:
> 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
|||"theintrepidfox" <theintrepidfox@.hotmail.com> wrote in message
news:9cb60b5b-5160-4afe-8555-8ed2bed12b09@.s36g2000prg.googlegroups.com...
> On 27 Nov, 13:46, theintrepidfox <theintrepid...@.hotmail.com> wrote:
> 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
|||Not really, but you may try adding an entry to your host file pointing to
your local box and using the loopback IP. My vague guess is that possibly
you're getting into a situation where you get an IP through VPN and it
doesn't resolve the new IP when you get disconnected. Mind you, that's just
a guess, but it's all I've got right now.
Anyway, try the host file thing and see if that does anything for you.
"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
>
>

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!

NeilOn 26 Nov, 10:15, "Neil" <nos...@.nospam.netwrote:

Quote:

Originally Posted by

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|||On 27 Nov, 13:46, theintrepidfox <theintrepid...@.hotmail.comwrote:

Quote:

Originally Posted by

On 26 Nov, 10:15, "Neil" <nos...@.nospam.netwrote:
>
>
>
>
>

Quote:

Originally Posted by

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.

>

Quote:

Originally Posted by

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.

>

Quote:

Originally Posted by

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.

>

Quote:

Originally Posted by

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

>

Quote:

Originally Posted by

Any ideas as to what's going on?

>

Quote:

Originally Posted by

Thanks!

>

Quote:

Originally Posted by

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.|||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" <theintrepidfox@.hotmail.comwrote in message
news:3e278590-302d-4549-82d4-2e12c0b51b1a@.i29g2000prf.googlegroups.com...

Quote:

Originally Posted by

On 26 Nov, 10:15, "Neil" <nos...@.nospam.netwrote:

Quote:

Originally Posted by

>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

|||"theintrepidfox" <theintrepidfox@.hotmail.comwrote in message
news:9cb60b5b-5160-4afe-8555-8ed2bed12b09@.s36g2000prg.googlegroups.com...

Quote:

Originally Posted by

On 27 Nov, 13:46, theintrepidfox <theintrepid...@.hotmail.comwrote:

Quote:

Originally Posted by

>On 26 Nov, 10:15, "Neil" <nos...@.nospam.netwrote:
>>
>>
>>
>>
>>

Quote:

Originally Posted by

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.

>>

Quote:

Originally Posted by

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.

>>

Quote:

Originally Posted by

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.

>>

Quote:

Originally Posted by

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

>>

Quote:

Originally Posted by

Any ideas as to what's going on?

>>

Quote:

Originally Posted by

Thanks!

>>

Quote:

Originally Posted by

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

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!
NeilOn 26 Nov, 10:15, "Neil" <nos...@.nospam.net> 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 remo
te
> 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 SQ
L
> 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 ge
t
> 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 SQ
L
> Server or the ODBC driver or something in the mix is looking at that remot
e
> database as part of what I'm using. Then, when the VPN connection is close
d,
> 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|||On 27 Nov, 13:46, theintrepidfox <theintrepid...@.hotmail.com> wrote:
> On 26 Nov, 10:15, "Neil" <nos...@.nospam.net> wrote:
>
>
>
>
>
>
>
>
>
> 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.|||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" <theintrepidfox@.hotmail.com> wrote in message
news:3e278590-302d-4549-82d4-2e12c0b51b1a@.i29g2000prf.googlegroups.com...
> On 26 Nov, 10:15, "Neil" <nos...@.nospam.net> wrote:
> 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|||"theintrepidfox" <theintrepidfox@.hotmail.com> wrote in message
news:9cb60b5b-5160-4afe-8555-8ed2bed12b09@.s36g2000prg.googlegroups.com...
> On 27 Nov, 13:46, theintrepidfox <theintrepid...@.hotmail.com> wrote:
> 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|||Not really, but you may try adding an entry to your host file pointing to
your local box and using the loopback IP. My vague guess is that possibly
you're getting into a situation where you get an IP through VPN and it
doesn't resolve the new IP when you get disconnected. Mind you, that's just
a guess, but it's all I've got right now.
Anyway, try the host file thing and see if that does anything for you.
"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 remo
te
> 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 SQ
L
> 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 ge
t
> 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 SQ
L
> Server or the ODBC driver or something in the mix is looking at that remot
e
> database as part of what I'm using. Then, when the VPN connection is close
d,
> 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
>
>