If its a matter of distributing new forms or objects, I would have the
DB with the autoexec handle copying the new objects. That way you don't
have to deal with bypassing the Autoexec. If you've got a split db, you
can set things up to have code check to see wether or not new objects
exist and if so which ones need to be copying. It might be as simple as
creating a table - tblNewObjects with a two fields - txtObjectName,
txtObjectType that lists the objects to copy.
Martin wrote:
> Thank you all.
>
> I am bypassing the autoexec so I can update the forms. For everyone else I
> want the autoexec to run on open.
>
> I will try and get it working and copy the code to the replies if it works.
>
> Thanks for your time once again.
>
> Martin
>
> "RD" wrote:
>
>
>>On Wed, 22 Jun 2005 12:07:05 -0700, Martin <(E-Mail Removed)>
>>wrote:
>>
>>
>>>Hello,
>>>
>>>I would like to write some code that will open a database using the
>>>OpenCurrentDatabase method. However the database I am opening has an
>>>autoexec macro that opens a form.
>>>
>>>My questions is how can I bypass the autoexec using the OpenCurrentDatabase
>>>method?
>>>
>>>Many thanks - this site is invaluable it really is.
>>>
>>>Martin
>>
>>Take a look at this and see if it helps:
>>http://www.mvps.org/access/api/api0068.htm
>>
>>Regards,
>>RD
>>
>>