Tony"s Auto FE updater and Runtime
Tony"s Auto FE updater and Runtime
am 06.09.2007 04:17:37 von Don Barton
Does anyone know if Tony Toews Auto FE updater utility work with the
new Access 2007 Runtime? I am new to using the runtime, but have
clients starting to ask for it. (they don't want to have to buy MS
Access). I presently use mdb/mde and Tony's utility together with
excellent results. If I create the FE as a runtime, can I still use
Tony's utility to update the font end as needed? I am trying to think
ahead, as I begin to implement an runtime solution.
Thanks,
Don
Re: Tony"s Auto FE updater and Runtime
am 06.09.2007 04:50:36 von Tony Toews
Don Barton wrote:
>Does anyone know if Tony Toews Auto FE updater utility work with the
>new Access 2007 Runtime? I am new to using the runtime, but have
>clients starting to ask for it. (they don't want to have to buy MS
>Access). I presently use mdb/mde and Tony's utility together with
>excellent results. If I create the FE as a runtime, can I still use
>Tony's utility to update the font end as needed? I am trying to think
>ahead, as I begin to implement an runtime solution.
Should work just fine. I have tested the Auto FE Updater with with Access 2007 and
also Windows Vista. Took me four days of hard digging to locate the Vista "issues".
The solution was ten minutes of code but hey that's how it goes.
That said I must admit I didn't test it with the A2007 runtime. Famous last words
but I can't see how that'll be a problem.
BTW what improvements would you like to see in the Auto FE Updater?
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Re: Tony"s Auto FE updater and Runtime
am 07.09.2007 06:03:13 von Don Barton
On Sep 5, 8:50 pm, "Tony Toews [MVP]" wrote:
> That said I must admit I didn't test it with the A2007 runtime. Famous last words
> but I can't see how that'll be a problem.
>
> BTW what improvements would you like to see in the Auto FE Updater?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
Hi Tony,
Re: AFEU, the only thing I've haven't been able to get to work
consistently is the GUI. Sometimes it's invoked so I can select a ini
file, verify it, and select an icon to use. Other times, it doesn't
appear at all and I edit the ini file as necessary. Not a big deal,
but it does save time and make things a little easier.
Re: Runtime. I think I have it just about figured out except for when
the absolute path is used to point to MSAccess.exe. (Drive Letter
example ini). What would be done in this case - since the client
doesn't have MSACCESS.exe ? Do we point to the Runtime file
somewhere? I haven't seen where this can be done yet.
Where the absolute path is not necessary to define, do we invoke the
Runtime by just using the command switch (\Runtime) by adding it to
the command line (in the ini file). Is it that simple when the client
does not have MS Access?
All my computers have either A2000, A2003, or A2007 installed, so I
haven't been able to test the package on an Access-less computer
yet.
Thanks in advance,
Don
Re: Tony"s Auto FE updater and Runtime
am 07.09.2007 20:12:25 von Tony Toews
Don Barton wrote:
>Re: AFEU, the only thing I've haven't been able to get to work
>consistently is the GUI. Sometimes it's invoked so I can select a ini
>file, verify it, and select an icon to use. Other times, it doesn't
>appear at all and I edit the ini file as necessary. Not a big deal,
>but it does save time and make things a little easier.
The GUI screen appears when your work station name is in the master.ini file and you
click on startmdb.exe to execute it.
>Re: Runtime. I think I have it just about figured out except for when
>the absolute path is used to point to MSAccess.exe. (Drive Letter
>example ini). What would be done in this case - since the client
>doesn't have MSACCESS.exe ? Do we point to the Runtime file
>somewhere?
Yes.
>I haven't seen where this can be done yet.
>Where the absolute path is not necessary to define, do we invoke the
>Runtime by just using the command switch (\Runtime) by adding it to
>the command line (in the ini file). Is it that simple when the client
>does not have MS Access?
As far as the Auto FE Updater is concerned there is no difference in the
configuration between regular Accesa and runtime Access. Except that you must have
the path to msaccess.exe specified when you use the StartMethod=FilePath option.
That path would be different for the runtime.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Re: Tony"s Auto FE Updater
am 04.04.2008 22:51:55 von BobH
On Mar 27, 1:24=A0am, "Tony Toews [MVP]" wrote:
> bobh wrote:
> >but if I change it to this, it hangs up my pc and I have to reboot,
> >why?
>
> Yowzer. =A0That's certainly not nice.
>
> Can you email me your INI file and I'll take a look at it? =A0
>
> What happens when, from your workstation, you click on the startmdb.exe on=
the
> server? =A0Do you see the INI files in the list box? =A0Does the Validate =
INI File button
> work? =A0Hows about the Run INI file button?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> =A0 =A0Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> =A0 =A0Microsoft Access Links, Hints, Tips & Accounting Systems athttp://w=
ww.granite.ab.ca/accsmstr.htm
> =A0 =A0Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
I hope you can help with this one.............
I tried to distribute desktop shortcuts using the FE Updater for one
of my applications since it had local and remote users. It seemed to
work yesterday but today nothing worked. I had to re-distribute a new
desktop shortcut and use the old method(all users point to the db on
the server).
her is what happened when I tried to use the desktop shortcut create
by the StartMDB.exe program
A dos prompt window opens with the following line in it.
C:\Progra~1\E!PC\HLLINIT.SYS
then, a message box pops up with
message box title =3D 16bit MS-DOS Subsystem
message box text
C:\Documents and Settings\RAH999\Desktop\EOR Bills.lnk
The NTVDM CPU has encountered an illegal instruction.
CS:)a8d IP:001e OP:ff ff ff ff ff Choose 'Close' to terminate the
application.
any ideas what this is all about???
bobh.