i've got a ms access mdb connected to a sql server on the internet.
whats the quickest way to get the ipaddress on the client machine from
the client machine? since there is a existing connection, shudn't there
be a simple method call that returns the ipaddress on the connection or
something?
the solutions i've seen r very ugly :(
riyazYou can get the MAC address of the client by doing this...
select net_address from master..sysprocesses where spid = @.@.spid
You then need to do processing outside of SQL Server in order to relate the
net_address to an IP address.
Tony.
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
<rmanchu@.gmail.com> wrote in message
news:1137653314.617807.262180@.g43g2000cwa.googlegroups.com...
> i've got a ms access mdb connected to a sql server on the internet.
> whats the quickest way to get the ipaddress on the client machine from
> the client machine? since there is a existing connection, shudn't there
> be a simple method call that returns the ipaddress on the connection or
> something?
> the solutions i've seen r very ugly :(
> riyaz
>|||yup i'm already getting the mac address like that. but i can't find any
clean function that relates the mac to the ipaddr. the code on the
mvp.org site returns a collection which i don't think can be related to
the mac
how can this be done?
? possible bug?
!!! i noticed the following when using access2003 over the internet to
sqlserver2000 !!!
when using my laptop with wifi, the net_address returned by
sysprocesses is INCORRECT. it returns my LAN mac_address when it shud
return my wifi mac_address since i'm connected the internet thru wifi.
can anybody duplicate this?
riyaz|||>> yup i'm already getting the mac address like that. but i can't find any
All you have to do is to use the address resolution protocol mapping. On
your command prompt, simply type in ARP -a. It should give you a table of
mapping between all MAC & IP addresses.
It is not that hard to get this information from t-SQL ( script or within a
procedure )using master..xp_cmdshell & get the IP address.
Anith|||hi.
> You can get the MAC address of the client by doing this...
> select net_address from master..sysprocesses where spid = @.@.spid
am already doing this
> You then need to do processing outside of SQL Server in order to relate th
e
> net_address to an IP address.
am working in access2003. could u give me an idea as to how i might go
about doing this?
i have 2 ip-addresses both dynamically allocated. i wud prefer a
general solution
riyaz|||I wrote this here just for you:
CREATE PROCEDURE usp_getboundAddresses
AS
BEGIN
SET NOCOUNT ON
IF OBJECT_ID('tempdb..#SomeTable') IS NULL
CREATE TABLE #SomeTable
(
ShellOutput VARCHAR(500)
)
INSERT INTO #SomeTable
EXEC xp_cmdshell 'nbtstat -a .'
SELECT
SUBSTRING( ShellOutput,
CHARINDEX('[',ShellOutput)+1,
LEN(ShellOutput) - CHARINDEX(']',ShellOutput) -2
) AS BoundAddress
from #SomeTable
WHERE ShellOutput LIKE '%Node IpAddress%' --the important lines
AND ShellOutput NOT LIKE '%0.0.0.0%' --Unassigned addresses
DROP TABLE #SomeTable
END
Returning the network adresses of the server.
HTH, Jens Suessmeyer.
Showing posts with label mdb. Show all posts
Showing posts with label mdb. Show all posts
Friday, February 24, 2012
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
>
>
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.
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.
>
>
>
>
>
>
>
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.
>
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...
>>
>>
>>
>>
>>
>>
>>
>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.
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
>
>
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
>
>
Subscribe to:
Posts (Atom)