Access 2007 Runtime

[Dave]

Hi -

Having last used the runtime with Access 97, clearly there are many
changes that I have to adjust to,

I have the following setup :

1 An Access database where the data has been split from the front-end.
2. I have code in-place that runs when the database loads and if it
cannot connect to the data - it attemts to locate the data file in
the apps current directoty and re-connect links.

3. When I run the database as normal (either by running the database
normally - or using the /runtime switch) the database loads fine (and
re-connects the data if necessary)

4. I then creating an installation routine and selected the "runtime"
options - where the runtime version is installed regardless.

5. The problem is - when I install and run the application - the
runtime engine complains about not being able to connect to the data
file (the code to re-attach the tables is not run.)

Could anyone help mw with this problem please ?

Cheers..

Dave.

P.S Am i going to also have security issues every time the applicaiton
is ran ? I mean, is it going to prompt the user everytime it loads as
to whether to trust the application ?

OS : Windows XP Service Pack 2
Delphi : 2005 Service Pack 3 Installed
CPU : AMD 3500+

[Douglas J. Steele]

Access 2007 requires that the database location be in a Trusted Location
before it'll run code.

Check what Jeff Conrad has at http://accessjunkie.com/faq_33.aspx for how to
do this with the runtime.

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

"Dave" <nos...@spamexcepmt.com> wrote in message
news:vrj4m557qmfgn965p...@4ax.com...

[Dave]

Ok thanks Doug -

After posting here, I trawled the net some more and found this issue
with regards "trusted" locations and did wonder if this was involved.

Looks Like I may need to modify the registry prior to running the
code.

I have a cunning plan :)

Cheers for help m8.

Dave.

On Fri, 29 Jan 2010 17:41:15 -0500, "Douglas J. Steele"
<NOSPAM_djsteele@NOSPAM_gmail.com> wrote:

>Doug

[Dave]

Hi Again -

Sorry to be a pest, but is there anywhere that describes the constants
that can be used in the Developer ditribution Wizard with regards the
registry values ?

For example, in Inno Setup (and other installers) they can use
constants to refer to information that may be useful when installing -
such as :

[installdir] would refer to the directory the user finally decided to
install the software to.

That was I could use the installer to add this to the relevant
registry entry to add it to the trusted locations.

I could put a constant in here, but if the user deciedes to install
the software elsewhere - this is going to be useless.

Any pointers much appreciated :)

Cheers..

Dave

[Douglas J. Steele]

Sorry, I've never used the Developer's Distribution Wizard, so I can't offer
any suggestions.

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

"Dave" <nos...@spamexcepmt.com> wrote in message

news:djv7m55k0msab3msq...@4ax.com...

[Dave]

Ok, thanks v much foryour time anyway :)

If I could only find some way to either capture the install directory
or even configure the wizard to call an external program (installed to
the same location) I could have this external App make the necessay
registry changes manually.

As it is, there is only the option to calla macro of VBA code ? Maybe
I need to look into this,,

Anyway, if anyone else can offer any suggestions - woul dbe much
appreciated.

Cheers..

On Sat, 30 Jan 2010 16:11:16 -0500, "Douglas J. Steele"
<NOSPAM_djsteele@NOSPAM_gmail.com> wrote:

>Sorry, I've never used the Developer's Distribution Wizard, so I can't offer
>any suggestions.

OS : Windows XP Service Pack 2

[Jay]

I don't believe it is a Trusted Location or Registry issue. I just
recently have come across the exact same problem.

I have an A2007 app that is at V3 and has over 200 runtime installs. It
installs to the MyDocuments folder which is a trusted location by
default (and the folder I am working with is a Trusted Location in any
event). For V3 of my app the relinking function has worked correctly. I
am now working on V4 and have come across the problem described. I
thought perhaps I introduced in while programming. I have created an
Autoexec macro to immediately call my re-linking function but 2007
Runtime is triggering the error (3024) before any code is called. The
interesting thing is that if after I get the error I close the accdr and
then re-open it the code runs and the back end re-links properly. This
only began happening about 1-2 months ago.

Is it possible that MS introduced a runtime bug in a recent SP update?

[Jay]

Figured out the problem (with the help of Dirk Goldgar, Access MVP).

You need to remove your start up form from the Access Options/Current
Database menu. Then create an Autoexec macro which first calls your
re-linking function and then opens your start upform. Evidently Access
Runtime loads the startup form (in the Current Database menu) first
(before running the Autoexec) and then doesn't recognize the links to
the backend so it kicks out the error before running the Autoexec.

[aleta]

derick vital zip 70591 dell run sonw

[me yuz]

rtyuioi_učy-t(-yčuop

"Dave" <nos...@spamexcepmt.com> a écrit dans le message de groupe de
discussion : vrj4m557qmfgn965p...@4ax.com...

[lexis f]

thank u but can some1 please tell me how to get everything set up

"Dave" <nos...@spamexcepmt.com> wrote in message

news:vrj4m557qmfgn965p...@4ax.com...

[marcy]

"lexis f" <chcolate...@yahoo.com> escreveu na mensagem
news:12957A34-0E9C-460C...@microsoft.com...