Forgive the potentially duplicative question, however, I feel it is unique.
I appreciate all the work done by Steven Lebans and his Browse CallBack,
however, in order to prevent errors, it must reside in the form.

I have many forms and it appears I must have lots of duplicative code as I
should place the calls as private in each form.

Has anyone come up with independent code that can be placed in a general
module that will accept a starting location?

Jerry

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...dules/200708/1

I don't see any reason why Stephen's code must reside in the form.

What issue are you seeing?

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


"jer99 via AccessMonster.com" <u27295@uwe> wrote in message
news:760cfb1f27aec@uwe...
> Forgive the potentially duplicative question, however, I feel it is
> unique.
> I appreciate all the work done by Steven Lebans and his Browse CallBack,
> however, in order to prevent errors, it must reside in the form.
>
> I have many forms and it appears I must have lots of duplicative code as I
> should place the calls as private in each form.
>
> Has anyone come up with independent code that can be placed in a general
> module that will accept a starting location?
>
> Jerry
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...dules/200708/1
>

on his site :
Bug Fix! June 13/2003 The calling functions must reside in the Form's Class
module or you will GPF at intermittent times. Thanks to Richard Bernstein for
the head up!
I'm taking it to mean the following functions:
BrowsePath
BrowseForFolderByPath
BrowseForFolderByPIDL
GetPIDLFromPath
IsWinNT()

Am I over-reacting?

Douglas J. Steele wrote:
>I don't see any reason why Stephen's code must reside in the form.
>
>What issue are you seeing?
>
>> Forgive the potentially duplicative question, however, I feel it is
>> unique.
>[quoted text clipped - 8 lines]
>>
>> Jerry

--
Message posted via http://www.accessmonster.com

Hmm. I missed that notice.

I guess I've just been lucky!

You could, I suppose, add everything to a single form, then add that form as
a subform everywhere else you need it.

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


"jer99 via AccessMonster.com" <u27295@uwe> wrote in message
news:760d89f9390a4@uwe...
> on his site :
> Bug Fix! June 13/2003 The calling functions must reside in the Form's
> Class
> module or you will GPF at intermittent times. Thanks to Richard Bernstein
> for
> the head up!
> I'm taking it to mean the following functions:
> BrowsePath
> BrowseForFolderByPath
> BrowseForFolderByPIDL
> GetPIDLFromPath
> IsWinNT()
>
> Am I over-reacting?
>
> Douglas J. Steele wrote:
>>I don't see any reason why Stephen's code must reside in the form.
>>
>>What issue are you seeing?
>>
>>> Forgive the potentially duplicative question, however, I feel it is
>>> unique.
>>[quoted text clipped - 8 lines]
>>>
>>> Jerry
>
> --
> Message posted via http://www.accessmonster.com
>