simulate network server locally

[Helmut]

Hello, I am Helmut,

developing Access 2000, SP3, with Frontend and Backend hosted in Italy
(via Citrix), english W2K Server, accessed by W2K Terminal.
Development is in Germany. German W2k Professional. Now the italian
admin added additional access possibilities to users in UK. He did it
with a Link. So my linked tables are no more named: H:\Customers, but:
\\servername\WorkgroupsD.

To work at home I finally found (don't remember the miracle any more,
there was something with entering a path into a grey area like
properties..?) a method to add a Link to the Drive H: in the Network
Environment, named WorkgroupsD. I named the local PC to the
servername.

This worked for a while. Two days after, the path was not found any
more.
Even if I display the properties of the Start button in the desktop -
needed for the secured database, the execute in: ...Path... shows a
message: path not valid.
Compress and repair of the database was not possible since
installation of the PC. So I did it on my laptop and called him
"servername" as well. But even there I am not able to open the
database, or install a link in the network environment to point to H:
Home Network is now disconnected.

Short version:
I want to access my linked tables on a stand alone machine with
\\computername\WorkgroupsD to produce access to my H: drive.
And the linked tables have to have this @!*-name.

Help could make me happy
Helmut

[Trevor Best]

Helmut wrote:

Short version:
I want to access my linked tables on a stand alone machine with
\\computername\WorkgroupsD to produce access to my H: drive.
And the linked tables have to have this @!*-name.

No need to go to all that trouble, just use the linked table manager to
connect up the tables locally while working at home?

--
This sig left intentionally blank

[Helmut]

Trevor Best <no****@besty.org.uk> wrote in message news:<42**********************@news.zen.co.uk>...

Helmut wrote:

Short version:
I want to access my linked tables on a stand alone machine with
\\computername\WorkgroupsD to produce access to my H: drive.
And the linked tables have to have this @!*-name.

No need to go to all that trouble, just use the linked table manager to
connect up the tables locally while working at home?

Hi, Trevor,

thank you for the nice idea with the linked tables, but I have to work
also on my own Laptop, without network connection.

When I take my copy from the life System (running in Italy), then I
cannot open it on my Laptop. Before I put my copy - as a secured
Database - back to the system, I have to show it to my customer first
- stand alone.

In the meantime I connected my PC/Laptop at home to my network, and it
opened the database. So the problem is reduced to a single offline PC.

Should I create a loopback? Or is there a network simulating hardware
plug?

Helmut

[Trevor Best]

Helmut wrote:

Trevor Best <no****@besty.org.uk> wrote in message news:<42**********************@news.zen.co.uk>...

Helmut wrote:

Short version:
I want to access my linked tables on a stand alone machine with
\\computername\WorkgroupsD to produce access to my H: drive.
And the linked tables have to have this @!*-name.

No need to go to all that trouble, just use the linked table manager to
connect up the tables locally while working at home?

Hi, Trevor,

thank you for the nice idea with the linked tables, but I have to work
also on my own Laptop, without network connection.

When I take my copy from the life System (running in Italy), then I
cannot open it on my Laptop. Before I put my copy - as a secured
Database - back to the system, I have to show it to my customer first
- stand alone.

In the meantime I connected my PC/Laptop at home to my network, and it
opened the database. So the problem is reduced to a single offline PC.

Should I create a loopback? Or is there a network simulating hardware
plug?

You don't need a network to run it standalone :-\

When you re-connect the tables, use a local path instead of a network path.

--
This sig left intentionally blank

[Helmut]

Trevor Best <no****@besty.org.uk> wrote in message news:<42**********************@news.zen.co.uk>...

Helmut wrote:

Trevor Best <no****@besty.org.uk> wrote in message news:<42**********************@news.zen.co.uk>...

Short version:
I want to access my linked tables on a stand alone machine with
\\computername\WorkgroupsD to produce access to my H: drive.
And the linked tables have to have this @!*-name.

You don't need a network to run it standalone :-\

When you re-connect the tables, use a local path instead of a network path.

Hi Trevor,

thank you for your support. I really appreciate it.
When I try to open the database on the standalone Laptop I cannot open
it at all.
I really have to create a link to the subdirectory in the network
environment. When I compare it with my second PC I see, that the
rightclick to the network environment does not give me the item:
create link. I will give the laptop the name of the server and connect
to another pc with a different name. Perhaps then I will be able to
create this missing link.

Success will happen soon... Helmut.

[Helmut]

Trevor Best <no****@besty.org.uk> wrote in message news:<42**********************@news.zen.co.uk>...

Helmut wrote:

Trevor Best <no****@besty.org.uk> wrote in message news:<42**********************@news.zen.co.uk>...

Hi, Trevor,

now I could connect my stand-alone laptop or PC even with this
server-oriented Path in the table connections. It was only necessary
to connect my PC as a single machine to the switch and the network
connection was ok. The tables in the backend stayed with their
original \\servername\drivename so I could open my database, when I
copied it from the original server to my laptop or PC - all I need to
carry with me is the switch.

thank you for supporting me anyway, your energy brought me to success.

Helmut