From: Douglas J. Steele on
Take a look at http://www.mvps.org/access/api/api0003.htm at "The Access
Web" for information about determining the details about mapped drives.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Dennis" <Dennis(a)discussions.microsoft.com> wrote in message
news:BA51DB9F-27D5-4685-A1B8-9D143C961E16(a)microsoft.com...
> Douglas,
>
> Your comments:
> So you're storing the full path to the file, and now the file doesn't
> exist
> in that location?
>
> Just store the name of the file and derive the location using the API
> call.
> That should work for both current users and future users.
>
>
> Response:
> First let me apologize for not having all of the information in the first
> question. The truth is I had not though about all of the different
> senarios
> that your response is making me think of now.
>
> No, that will not work either. I just found out today that some of the
> users are NOT storing their documents in Windows' "My Document"
> directories.
> Some of my users are storing their documents in their own directory
> structure
> completely outside of "My Documents". They are using directory structures
> such as C:\Customer\<CustName>\....". The documents that are scanned in
> goto
> "C:\Scan\<scan date>\...". And in stead of the C drive, the data might be
> on
> the network. Using the derived locations will not help in these case.
>
> That is why I figure I will have to parse the path name. If it is the XP
> or
> Vista "MY Doc" structure, then I will have to figure out a way to store
> that
> information. If it is not part of the "MY Doc" structure, then I will
> have
> to store the full path name.
>
> Also, I have to figure out if I want to store the network drive leter
> (which
> I don't think I want to as different computer could have the same drive
> letters pointing to different directories, which the should not but who
> knows).
>
> Ahhhh, the more I think about it the uglier it gets.
>
> From Access, can I tell if a drive is local or a network drive?
> If I can tell, can I get the true name path (DNS path? - sorry don't know
> the correct techincal term) - ie. U: really is "\\SBS2003\share"
>
> Again, my apoligize for not having thought this all the way through.
> Unless someone else brings up another angle I have not though about, I
> think
> I have provided all of the information you might need. But then again,
> watch
> me be proven wrong.
>
> Thanks for you assitance.
>
> Dennis


From: Dennis on
David,

My Question: What is your advice for where to place the front end software?

Your Response: In the user's profile, one copy for each user of the
machine. There's no disk space issue any longer, so it's a waste of time to
be worrying about multiple copies of the front end on the same machine, one
for each user logon.


I don't understand this response. If I put one FE in each user's profile,
that I have multiple copies of the code on the machine. I do not want to do
this. I can see putting the code in the Programs directory, but not in each
person's profile.

Since you say there multiple copies are a non-issue, I don't understand your
answer.

I'm missing something, but I don't know what it is. I don't understand how
I can put a FE in each user's profile and not have duplicate copies of the
code.

Could you explain this?

Thanks,

Dennis

From: Dennis on
Douglas,

Thanks for the link.

Any suggestions on how to deal with storing the different path names between
Xp & Vista / Win 7?


Dennis

From: Douglas J. Steele on
Is the issue that you've got users who populated the table when they were
running XP and now that they've moved to Visat/Win7, the application doesn't
work? How can you be certain that the necessary files migrated from XP with
the user?

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
(no e-mails, please!)

"Dennis" <Dennis(a)discussions.microsoft.com> wrote in message
news:A732808A-3F8A-4E8E-A39F-8DDB2AEC969F(a)microsoft.com...
> Douglas,
>
> Thanks for the link.
>
> Any suggestions on how to deal with storing the different path names
> between
> Xp & Vista / Win 7?
>
>
> Dennis
>


From: David W. Fenton on
=?Utf-8?B?RGVubmlz?= <Dennis(a)discussions.microsoft.com> wrote in
news:C03B514B-B38C-4286-A195-0FC20E128EAE(a)microsoft.com:

> My Question: What is your advice for where to place the front end
> software?
>
> Your Response: In the user's profile, one copy for each user of
> the machine. There's no disk space issue any longer, so it's a
> waste of time to be worrying about multiple copies of the front
> end on the same machine, one for each user logon.
>
> I don't understand this response. If I put one FE in each user's
> profile, that I have multiple copies of the code on the machine.
> I do not want to do this. I can see putting the code in the
> Programs directory, but not in each person's profile.
>
> Since you say there multiple copies are a non-issue, I don't
> understand your answer.
>
> I'm missing something, but I don't know what it is. I don't
> understand how I can put a FE in each user's profile and not have
> duplicate copies of the code.

I didn't say you wouldn't have multiple copies. I said multiple
copies are not a problem, and they aren't.

Of course, I assume you have some automated method of pushing out
updates to the front end like Tony Toews's AutoFE Updater
(http://www.autofeupdater.com/). If you are doing it manually, that
can become messy, but you simply shouldn't be doing it manually,
particularly when there are multiple users on each machine (I don't
have many clients with that setup, so I do have some clients with
non-automated front-end updates).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/