From: HarkitsMark on
I have a runtime/accde app to be distributed to users that can't have access
to the nav pane or objects, and even though I've disabled special keys,
including shift keys, and turned off the nav pane option, the nav pane
reappears during app startup. Found out using docmd.transferdatabase acLink
is the culprit.

1) does MS know about this and 2) what's the fix if I want to re-create
table connections during startup behind the scenes?
--
Mark A. Kann
Access Developer/Data Analyst
Rockford, IL
From: Maurice on
This is indeed a bug and there's no fix for it. Other solution i heard for
this problem is to use a timer, do the action (transfer) and after the
transfer hide the navepane via code again.

It's a workaround not a solution bu maybe it points you to a tem solution.
--
Maurice Ausum


"HarkitsMark" wrote:

> I have a runtime/accde app to be distributed to users that can't have access
> to the nav pane or objects, and even though I've disabled special keys,
> including shift keys, and turned off the nav pane option, the nav pane
> reappears during app startup. Found out using docmd.transferdatabase acLink
> is the culprit.
>
> 1) does MS know about this and 2) what's the fix if I want to re-create
> table connections during startup behind the scenes?
> --
> Mark A. Kann
> Access Developer/Data Analyst
> Rockford, IL
From: Rick Brandt on
HarkitsMark wrote:

> I have a runtime/accde app to be distributed to users that can't have
> access to the nav pane or objects, and even though I've disabled special
> keys, including shift keys, and turned off the nav pane option, the nav
> pane
> reappears during app startup. Found out using docmd.transferdatabase
> acLink is the culprit.
>
> 1) does MS know about this and 2) what's the fix if I want to re-create
> table connections during startup behind the scenes?

Use DAO to create the link instead of TransferDatabase.
From: HarkitsMark on
Rick

Interesting suggestion. Can you tell me what that DAO statement/code looks
like? Does this actually work or is it just an idea? Thanks


--
Mark A. Kann
Access Developer/Data Analyst
Rockford, IL


"Rick Brandt" wrote:

> HarkitsMark wrote:
>
> > I have a runtime/accde app to be distributed to users that can't have
> > access to the nav pane or objects, and even though I've disabled special
> > keys, including shift keys, and turned off the nav pane option, the nav
> > pane
> > reappears during app startup. Found out using docmd.transferdatabase
> > acLink is the culprit.
> >
> > 1) does MS know about this and 2) what's the fix if I want to re-create
> > table connections during startup behind the scenes?
>
> Use DAO to create the link instead of TransferDatabase.
> .
>
From: Armen Stein on
On Sat, 20 Mar 2010 20:34:01 -0700, HarkitsMark
<markkann(a)sbcglobal.net> wrote:

>
>Interesting suggestion. Can you tell me what that DAO statement/code looks
>like? Does this actually work or is it just an idea? Thanks

If you want an automated DAO approach to relinking tables, you're
welcome to use our free J Street Access Relinker on our J Street
Downloads page: http://ow.ly/M56Q

It handles multiple Access back-end databases, ignores ODBC linked
tables, and can automatically and silently relink to back-end
databases in the same folder as the application (handy for work
databases or single-user scenarios). There's a ReadMe table with
instructions.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com