split ascs.mdb file looking for z: drive

[Janis]

I have a split ascs_be.mdb and ascs.mdb file. The ascs_be.mdb interface file
opens the db and the other file the ascs.mdb has the access tables. The
opener file somehow has a wired path to the mapped drive and folder
z:SwimClub/ascs_be.mdb folder. I was given this db to write some scriptx
but I can't open it without a z: drive with that folder on it. I don't have
a network drive.
Is there a way I can open the file or do I have to have get a network drive?

 

[潇洒æ°æ°]

I have a split ascs_be.mdb and ascs.mdb file. The ascs_be.mdb interface
file
opens the db and the other file the ascs.mdb has the access tables. The
opener file somehow has a wired path to the mapped drive and folder
z:SwimClub/ascs_be.mdb folder. I was given this db to write some scriptx
but I can't open it without a z: drive with that folder on it. I don't
have
a network drive.
Is there a way I can open the file or do I have to have get a network
drive?

 

[Tom Wickerath]

Hi Janis,

The ascs_be.mdb interface file opens the db and the other file the
ascs.mdb has the access tables.

Usually, the file with "be" in its name indicates "back-end", which is the
file that contains the tables with the shared data.

Try opening your front-end (application) file while holding down the Shift
key the entire time the file is opening. Then use the linked table manager
(Tools | Database Utilities | Linked Table Manager in Access 2000/2002/2003)
to relink the tables. Select all tables, and check the option to always
prompt for new location. Then press the OK button and navigate to the BE
database.

Note: If you are using Access 2007, the steps to invoke the relinking wizard
are a bit different. Post back if that is the case, and I'll fire up A2007 to
determine the steps.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

 

[Arvin Meyer MVP]

You will need the back-end file either locally, or on the network drive. If
locally, use the Link Table Manager to relink the tables to the backend on
the local drive, or create a mapped drive to the network.

 

[潇洒æ°æ°]

I have a split ascs_be.mdb and ascs.mdb file. The ascs_be.mdb interface
file
opens the db and the other file the ascs.mdb has the access tables. The
opener file somehow has a wired path to the mapped drive and folder
z:SwimClub/ascs_be.mdb folder. I was given this db to write some scriptx
but I can't open it without a z: drive with that folder on it. I don't
have
a network drive.
Is there a way I can open the file or do I have to have get a network
drive?

 

[潇洒æ°æ°]

I have a split ascs_be.mdb and ascs.mdb file. The ascs_be.mdb interface
file
opens the db and the other file the ascs.mdb has the access tables. The
opener file somehow has a wired path to the mapped drive and folder
z:SwimClub/ascs_be.mdb folder. I was given this db to write some scriptx
but I can't open it without a z: drive with that folder on it. I don't
have
a network drive.
Is there a way I can open the file or do I have to have get a network
drive?

 

[Janis]

No I'm using 2003. Thanks.

Hi Janis,


Usually, the file with "be" in its name indicates "back-end", which is the
file that contains the tables with the shared data.

Try opening your front-end (application) file while holding down the Shift
key the entire time the file is opening. Then use the linked table manager
(Tools | Database Utilities | Linked Table Manager in Access 2000/2002/2003)
to relink the tables. Select all tables, and check the option to always
prompt for new location. Then press the OK button and navigate to the BE
database.

Note: If you are using Access 2007, the steps to invoke the relinking wizard
are a bit different. Post back if that is the case, and I'll fire up A2007 to
determine the steps.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

 

[aaron.kempf]

splitting will not make things simpler

upsizing to SQL Server _WILL_ make things simpler for you

 

[Arvin Meyer MVP]

splitting will not make things simpler

upsizing to SQL Server _WILL_ make things simpler for you

 

[aaron.kempf]

SQL Server is easy to install dude.. it is the most popular database
in the world.

so sorry that you think that putting a single install on a server is
_SOOOOOOO_____ hard you're full of shit.

it's simpler
it works

and you don't need to run around, refreshing linked tables-- every
time your customers open their frontend

what a waste, if only you knew the slightest thing about SQL Server

Correct Drivers?
Are you ****ing kidding me?

Jet drivers aren't even AVAILABLE for X64, the most popular version of
Vista

And SQL Server drivers come built in with MDAC---
unlike Jet-- they pulled Jet out of MDAC years ago.

You don't need to install anything other than MS Access on the front
end-- don't listen to this jack-ass'es hysteria



-aaron

splitting will not make things simpler

upsizing to SQL Server _WILL_ make things simpler for you

---------------
Actually, not true at all. First you have a second installation (that of
SQL-Server on the server). Additionally, you must have the correct drivers
on the machine, that is ODBC and/or OLEDB. And you still must link the to
the back-end. That doesn't equate to simpler.
--

SA> Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com

 

[aaron.kempf]

must link to the backend?

I use ADP, exclusively... there is a single connection.

it's 1000 times simpler than your linked table bullshit.

**** you and your mis-information, bitch