Load Access From Default Drive?
in [Forms]
|
From: Scientific on 4 Jul 2008 21:02 Hello all, I have a multi-user database that I want to send to others so they can try it out. The problem I noticed though is the drive letter access looks for is the one I created the database on which is "G". Is there a way to tell Access to use the current drive (whatever the drive letter is) to load whatever files it needs to open the database? Right now I've been asking people which drive letter they're loading the database from, then going into the Linked Table Manager and changing the drive letter manually, what a pain. -S
From: Arvin Meyer [MVP] on 4 Jul 2008 21:11 The back-end should be on a server, and the front-end on their local drive. It usually shouldn't make a difference where the front-end is, and the back end should be mapped the same, or use the Universal Naming Convention to set it's location. \\ServerName\FolderName\DatabaseBackend.mdb -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com "Scientific" <Scientific(a)discussions.microsoft.com> wrote in message news:D260BBF4-8398-4C5C-977E-36E66525B32E(a)microsoft.com... > Hello all, > > I have a multi-user database that I want to send to others so they can try > it out. The problem I noticed though is the drive letter access looks for > is > the one I created the database on which is "G". Is there a way to tell > Access to use the current drive (whatever the drive letter is) to load > whatever files it needs to open the database? > > Right now I've been asking people which drive letter they're loading the > database from, then going into the Linked Table Manager and changing the > drive letter manually, what a pain. > > -S
From: Scientific on 4 Jul 2008 22:01 Arvin, Yea, that makes sense and the final database would be deployed that way. But just for testing purposes the backend and frontend reside on the same drive. I have it setup this way because others don't have Network access just yet. I just want them to be able to see if it works to their satisfaction before it gets deployed. They all work at different companies. What would you do in this situation Arvin? -S "Arvin Meyer [MVP]" wrote: > The back-end should be on a server, and the front-end on their local drive. > It usually shouldn't make a difference where the front-end is, and the back > end should be mapped the same, or use the Universal Naming Convention to set > it's location. > > \\ServerName\FolderName\DatabaseBackend.mdb > > -- > Arvin Meyer, MCP, MVP > http://www.datastrat.com > http://www.mvps.org/access > http://www.accessmvp.com > > "Scientific" <Scientific(a)discussions.microsoft.com> wrote in message > news:D260BBF4-8398-4C5C-977E-36E66525B32E(a)microsoft.com... > > Hello all, > > > > I have a multi-user database that I want to send to others so they can try > > it out. The problem I noticed though is the drive letter access looks for > > is > > the one I created the database on which is "G". Is there a way to tell > > Access to use the current drive (whatever the drive letter is) to load > > whatever files it needs to open the database? > > > > Right now I've been asking people which drive letter they're loading the > > database from, then going into the Linked Table Manager and changing the > > drive letter manually, what a pain. > > > > -S > > >
From: Arvin Meyer [MVP] on 4 Jul 2008 22:07 "Scientific" <Scientific(a)discussions.microsoft.com> wrote in message news:B89662C0-F0ED-4891-B2C7-D18B5E4A825F(a)microsoft.com... > Arvin, > > Yea, that makes sense and the final database would be deployed that way. > But just for testing purposes the backend and frontend reside on the same > drive. I have it setup this way because others don't have Network access > just yet. I just want them to be able to see if it works to their > satisfaction before it gets deployed. They all work at different > companies. > > What would you do in this situation Arvin? In that case, have everyone create a folder: C:\TestDB\ and put both files in it. If everyone has the same folder system, your work just got easier. You can write relink code that will set the path to: CurrentProject.Path you'll find some relink code at: http://www.mvps.org/access/tables/tbl0009.htm -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com
From: Scientific on 4 Jul 2008 22:50 Arvin, That's a brilliant idea and that should work for everyone. Man, I love this forum. Thanks a gazillion Arvin, I owe you big time. -S "Arvin Meyer [MVP]" wrote: > "Scientific" <Scientific(a)discussions.microsoft.com> wrote in message > news:B89662C0-F0ED-4891-B2C7-D18B5E4A825F(a)microsoft.com... > > Arvin, > > > > Yea, that makes sense and the final database would be deployed that way. > > But just for testing purposes the backend and frontend reside on the same > > drive. I have it setup this way because others don't have Network access > > just yet. I just want them to be able to see if it works to their > > satisfaction before it gets deployed. They all work at different > > companies. > > > > What would you do in this situation Arvin? > > In that case, have everyone create a folder: > > C:\TestDB\ > > and put both files in it. If everyone has the same folder system, your work > just got easier. > > You can write relink code that will set the path to: > > CurrentProject.Path > > you'll find some relink code at: > > http://www.mvps.org/access/tables/tbl0009.htm > -- > Arvin Meyer, MCP, MVP > http://www.datastrat.com > http://www.mvps.org/access > http://www.accessmvp.com > > >
|
Pages: 1 Prev: Case statement Problem Compile Error Next: Case statement Problem few more tries |