From: Jörn Bosse on
Well,

try to create a button which executes the code. I just checked ist and
it works fine. If that doesn�t hel, you may create a module with a
public function. Create a macro called autoexec which executes this
function.
You could show up a messagbox when loading your startform to check if
code is about to be executed on startup.

J�rn

Am 04.06.2010 23:46, schrieb esn:
> Thanks for checking in again,
>
>> Did you create a secure folder in the security center? Or do you always
>> have to choose "Allow Macros" or something like this, when your db starts?
>
> The db is in a "trusted location," so events/macros aren't blocked,
> plus I have my default setting at "allow all macros" because the only
> db files I open are ones I built myself. Anything else it could be?

From: esn on
On Jun 4, 3:04 pm, Jörn Bosse <joernbo...(a)gmx.de> wrote:
> Well,
>
> try to create a button which executes the code. I just checked ist and
> it works fine. If that doesn´t hel, you may create a module with a
> public function. Create a macro called autoexec which executes this
> function.
> You could show up a messagbox when loading your startform to check if
> code is about to be executed on startup.
>
> Jörn
>
> Am 04.06.2010 23:46, schrieb esn:
>
> > Thanks for checking in again,
>
> >> Did you create a secure folder in the security center? Or do you always
> >>    have to choose "Allow Macros" or something like this, when your db starts?
>
> > The db is in a "trusted location," so events/macros aren't blocked,
> > plus I have my default setting at "allow all macros" because the only
> > db files I open are ones I built myself.  Anything else it could be?

I know the code is loading on startup because it hides the navigation
pane like it should. I tried putting the code in the on click event
of a button and it still doesn't do anything. I've pored over the
options and can't find anything that would be blocking this particular
line of code. Is there any chance I accidentally renamed the ribbon
or something like that?
From: esn on
On Jun 5, 11:15 am, esn <ericnewk...(a)gmail.com> wrote:
> On Jun 4, 3:04 pm, Jörn Bosse <joernbo...(a)gmx.de> wrote:
>
>
>
> > Well,
>
> > try to create a button which executes the code. I just checked ist and
> > it works fine. If that doesn´t hel, you may create a module with a
> > public function. Create a macro called autoexec which executes this
> > function.
> > You could show up a messagbox when loading your startform to check if
> > code is about to be executed on startup.
>
> > Jörn
>
> > Am 04.06.2010 23:46, schrieb esn:
>
> > > Thanks for checking in again,
>
> > >> Did you create a secure folder in the security center? Or do you always
> > >>    have to choose "Allow Macros" or something like this, when your db starts?
>
> > > The db is in a "trusted location," so events/macros aren't blocked,
> > > plus I have my default setting at "allow all macros" because the only
> > > db files I open are ones I built myself.  Anything else it could be?
>
> I know the code is loading on startup because it hides the navigation
> pane like it should.  I tried putting the code in the on click event
> of a button and it still doesn't do anything.  I've pored over the
> options and can't find anything that would be blocking this particular
> line of code.  Is there any chance I accidentally renamed the ribbon
> or something like that?

Update - I tried putting it on a form in a completely empty blank
database and it does the trick. So why is the database I'm working on
not reading that particular line of code? I took a look at some of
the system tables to see if anything jumped out but that's all way
over my head.
From: esn on
I just remembered having a problem with the VBA references of a
previous database file. I had to go into the tools menu and de-select
a few references, close, reopen, and re-select the referenced
libraries. Any chance this is something similar - some sort of broken
object reference or something? I tried running through this process,
but Access wouldn't let me remove the first two references in the
list, since there are objects that depend on them. Could the problem
be in one of those? If so, what do I do to fix it?
From: Jörn Bosse on
If you didn�t disabled the VBA Project ref everything should work with
that code. You cant change the name of the Ribbon toolbar at all. Would
you please try that code in an other db?
If you want to, you can send me that db, via email but please with no
data inside. Then i can figure out whats wrong and not only suggesting
what it could be. This would be a lot faster.

Regards
J�rn


Am 05.06.2010 20:51, schrieb esn:
> I just remembered having a problem with the VBA references of a
> previous database file. I had to go into the tools menu and de-select
> a few references, close, reopen, and re-select the referenced
> libraries. Any chance this is something similar - some sort of broken
> object reference or something? I tried running through this process,
> but Access wouldn't let me remove the first two references in the
> list, since there are objects that depend on them. Could the problem
> be in one of those? If so, what do I do to fix it?

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Imported Form Changes
Next: Forms or Tables