[AccessD] Leave a bound form in a library.

jwcolby jwcolby at colbyconsulting.com
Wed Sep 1 13:26:01 CDT 2010


Jim,

I am discussing where the data comes from that is displayed in the form.

John W. Colby
www.ColbyConsulting.com


Jim Lawrence wrote:
> John:
> 
> I have not been following this thread carefully but does not a form and/or
> module loaded/called from either the local MDB or a remote one, reside in
> memory until a unhandled error occurs or the FE MDB is exited?
> 
> Jim
> 
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Wednesday, September 01, 2010 10:10 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Leave a bound form in a library.
> 
> Shamil,
> 
> that workaround only has to be applied to the forms stored in my library.
> Obviously there is a 
> development cost but after that it works fine.  I don't have to do that for
> the forms in the 
> application that I am applying security to.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Shamil Salakhetdinov wrote:
>> John --
>>
>> I see. But then why rebinding form in Open or Load event to a query, which
>> uses IN '' clause, is considered as not so efficient workaround there?
>>
>> -- Shamil
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>> Sent: Wednesday, September 01, 2010 8:00 PM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] Leave a bound form in a library.
>>
>>  > Did that client have two FEs stored in the same folder?
>>
>> Yes.  Of course I can work around the issue but I prefer to have it "just
>> work".  Of course having 
>> the tables in the Fe itself introduces issues as well.  There is no free
>> lunch.
>>
>> John W. Colby
>> www.ColbyConsulting.com
>>
>>
>> Shamil Salakhetdinov wrote:
>>> John --
>>>
>>> Yes, I "mean linking the tables from the FE back into the lib".
>>> Why not "clone" library database for every FE?
>>> Did that client have two FEs stored in the same folder?
>>>
>>> -- Shamil
>>>
>>> -----Original Message-----
>>> From: accessd-bounces at databaseadvisors.com
>>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>>> Sent: Wednesday, September 01, 2010 9:38 AM
>>> To: Access Developers discussion and problem solving
>>> Subject: Re: [AccessD] Leave a bound form in a library.
>>>
>>> Shamil,
>>>
>>> I take it you mean linking the tables from the FE back into the lib so
>> that
>>> the form opens seeing 
>>> the security info for the FE.
>>>
>>> I did something like this but ended up with problems when the client
>> wanted
>>> to use the library for 
>>> two different FEs which needed different security info.
>>>
>>> John W. Colby
>>> www.ColbyConsulting.com
>>>
>>>
>>> Shamil Salakhetdinov wrote:
>>>> Hi John --
>>>>
>>>> What about linked tables?
>>>> I used them in library MS Access databases and that worked well for me
>> and
>>>> for my customers in many projects.
>>>>
>>>> Thank you.
>>>>
>>>> -- Shamil
>>>>
>>>> -----Original Message-----
>>>> From: accessd-bounces at databaseadvisors.com
>>>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
>>>> Sent: Wednesday, September 01, 2010 5:38 AM
>>>> To: Access Developers discussion and problem solving
>>>> Subject: [AccessD] Leave a bound form in a library.
>>>>
>>>> One of the challenges of using an "addin" library is placing forms in
> the
>>>> add-in but having them 
>>>> load records from the FE.  For example if I make a bound form to load
> the
>>>> users table but I leave 
>>>> that form in the library (add-in), then when the form opens it tries to
>>> load
>>>> the data from the table 
>>>> in the library.  IOW a form tries to pull its data from whatever
>> container
>>>> it is placed in.
>>>>
>>>> One way around that is to use the "in 'MyFePath\MyDbName.mdb' syntax
> that
>>> is
>>>> valid in access.  As an 
>>>> example SQL to pull the records from the FE might look as follows:
>>>>
>>>> SELECT * FROM usystblPLSObjFrm in 'C:\Dev\C2DbPLS\C2DbPLS.mda' ORDER BY
>>>> PLSF_Name;
>>>>
>>>> This would obviously pull all fields from the table usystblPLSObjFrm
>>>> physically located in 
>>>> C:\Dev\C2DbPLS\C2DbPLS.mda.
>>>>
>>>> This is a PITA and requires jumping through hoops but that is the only
>>>> solution that I know of.
>>>>
>>>> If any of you know of another solution please let me know since I do
> have
>>> to
>>>> get adept at hoop 
>>>> jumping to do it my way.
>>>>
>>>> Thanks,



More information about the AccessD mailing list