Problem with Tony's Auto FE updater

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Amit - 12 Jul 2005 23:37 GMT

Note: I'd posted this by mistake in forms-coding. So, if you see the same
post in the other forum, I was not trying to waste someone's time. Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Windows XP, MS Access 2K
====================
Hi,

I'm having some problems with running the StartMDB.exe from the AutoFE
utility provided by Tony.

I have split the database, and have FE and BE on the shared drive on the
server. I have copied the FE to the C: drive. The startup and INI files are
on the shared drive too.

I was able to successfully run the startMDB.exe file on MY desktop and
install the short-cut on my desktop, and it is working the way it's supposed
to.

When I tried to run startMDB.exe from another user's desktop, I got the
error message "Null command line prompt sent to utility."

Following the directions from Tony's web-site, I tried to re-run the exe
file using command line prompt, but got the message that the INI file is not
found. I've checked the folder, and the INI file is there.

One thing is that the directory path on the shared drive is pretty long, and
the sub-folder where the startMDB.exe and INI files reside, is 6 levels down.
Not sure if there is a limit to the number of characters that can be
specified.

Then, the next thing I tried is to copy the startup and the INI files on the
C: drive and tried to run it from there. This time, I got the following error
message:

The Desktop shortcut has the following for the first portion of the Target:
'S:\Shared\blahblah\Database\Startup Files\StartMDB.exe'
when it should be:
'C:\ITS Startup\StartMDB.exe'

The actual file is: 'C:\Documents and Settings\amit\Desktop\ITS'

---------- C:\ITS Startup\Getting Started.ini--------------------
[Settings]
MainApp=C:\ITS_FE\its3_FE.mdb
Server="S:\Shared\blahblah\Database\FrontEnd-Master\"
StartMethod=FilePath
Shell="C:\Program Files\Microsoft Office 2000\Office\MSACCESS.EXE"
Lockout=No
LockoutMsg=Sorry, the system is not accessible right now.
SupportMsg=Please contact your ITS support person for support.

ShortCutName=Information Tracking System
CreateShortCutOnDesktop=yes
CreateShortCutOnCommonDesktop=no
ShortCutIconFile=C:\WINDOWS\system32\shell32.dll
ShortCutIconFileIndex=130
--------------------------------------------------------------------------------
Auto FE Updater Version: 1.69
Windows Version: Windows XP 5.1 build 2600 (Service Pack 2)
User: Amit
Workstn: WS-F344
--------------------------------------------------------------------------------

If someone can help me with this, I'll appreciate it. I'm totally lost as to
why this is happening, and how to correct it....

Many thanks.

-Amit

Further update: I've re-downloaded the files, and run them again, with the
same result - when I run the file on my desktop, it works fine. When I try
and run it from someone else's desktop, I get the same error.

Reply to this Message

Tony Toews - 19 Jul 2005 05:09 GMT

>I was able to successfully run the startMDB.exe file on MY desktop and
>install the short-cut on my desktop, and it is working the way it's supposed
>to.

Good.

>When I tried to run startMDB.exe from another user's desktop, I got the
>error message "Null command line prompt sent to utility."

You need to run startMDB.exe with an INI file specified. One way of
doing this is to have the utility create a shortcut in the directory
on the server and have the users click on that shortcut.
Alternatively you or the utility can create a .cmd/.bat file again
with the same INI file specified.

Another option would be take the shortcut created on your desktop and
copy it to the server somewhere. And rename it to "Click here to
install XYZ app."

The problem is that somehow the user has to start the utility with the
name of the INI file passed to it.

>Following the directions from Tony's web-site, I tried to re-run the exe
>file using command line prompt, but got the message that the INI file is not
[quoted text clipped - 4 lines]
>Not sure if there is a limit to the number of characters that can be
>specified.

No, that won't be a problem.

>Then, the next thing I tried is to copy the startup and the INI files on the
>C: drive and tried to run it from there. This time, I got the following error
[quoted text clipped - 4 lines]
>when it should be:
>'C:\ITS Startup\StartMDB.exe'

Actually you want to leave the StartMDB.exe and the Getting
Started.INI file on the server. There's no reason to copy them to the
users system. After all if the server isn't available then nothings
going to work anyhow.

Tony

Signature

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

Reply to this Message

Amit - 19 Jul 2005 19:25 GMT

> >I was able to successfully run the startMDB.exe file on MY desktop and
> >install the short-cut on my desktop, and it is working the way it's supposed
[quoted text clipped - 17 lines]
> The problem is that somehow the user has to start the utility with the
> name of the INI file passed to it.

<snip>

Hi Tony,

Many thanks for responding. I was actually in the process of writing my own
updater (but not as sleek/robust/sophisticated as yours :) using an mdb file
to check for a latest file, and open the main mdb app. But, I think I'll try
what you suggested.

I still have a couple of questions after reading your response, and
re-reading the pages on your auto-FE updater website. Will appreciate it if
you can bear with me.

1. Do I have to run startMDB.exe from each user's desktop? From reading the
notes, it seems that I do, but I'm somewhat unsure now after reading your
response.

2. I'm not sure what you mean by "utility create a short-cut on the server".
Is this the short-cut for the main application, or short-cut to startMDB.exe
on the server??

3. If a second user clicks on startMDB.exe on the server, will that not
work? Do subsequent users have to click on the short-cut? Because I'm quite
sure I tried this and got the "null command line prompt" message. When that
didn't work, *then* I tried running startMDB.exe from the C: drive (after
copying it there).

When I ran startMDB.exe from my workstation, it did create a short-cut on my
desktop, and double-cliking on this short-cut opened the main application.
(this is different from the short-cut for startMDB.exe.)

Are you saying that all I've to do is copy this short-cut (for the
application) to the server, and then give people the path to it, and not run
startMDB.exe from each user's workstation?

I guess to me it's not clear which short-cut is being mentioned, and I do
apologize for my lack of Windows programming experience.

When I ran startMDB.exe from my desktop, it worked fine. So, do I repeat the
exact *same* steps for subsequent users (using their workstation), or is the
process for second (and subsequent) user(s) different?

Thanks Tony.

-Amit

Reply to this Message

Tony Toews - 22 Jul 2005 19:07 GMT

>I still have a couple of questions after reading your response, and
>re-reading the pages on your auto-FE updater website. Will appreciate it if
[quoted text clipped - 3 lines]
>notes, it seems that I do, but I'm somewhat unsure now after reading your
>response.

Not at all. Leave that file eon the server.

>2. I'm not sure what you mean by "utility create a short-cut on the server".
>Is this the short-cut for the main application, or short-cut to startMDB.exe
>on the server??

Ah, I mean a shortcut to the StartMDB.EXE file with the INI file name
in the target. For example "Q:\1_vb\StartMDB\StartMDB.exe /cmd
/inifile:"Q:\1_vb\StartMDB\Drive Letter Example.ini""

>3. If a second user clicks on startMDB.exe on the server, will that not
>work? Do subsequent users have to click on the short-cut? Because I'm quite
>sure I tried this and got the "null command line prompt" message. When that
>didn't work, *then* I tried running startMDB.exe from the C: drive (after
>copying it there).

You are the only person who clicks on StartMDB.exe. Everyone else
should be using a shortcut which contains a target line as per above
example. (Or you can create a .cmd/.bat file with the exact same text
in the file.)

>When I ran startMDB.exe from my workstation, it did create a short-cut on my
>desktop, and double-cliking on this short-cut opened the main application.
>(this is different from the short-cut for startMDB.exe.)

Great. That's the shortcut that the users should now be using.

>Are you saying that all I've to do is copy this short-cut (for the
>application) to the server, and then give people the path to it, and not run
>startMDB.exe from each user's workstation?

Correct.

>I guess to me it's not clear which short-cut is being mentioned, and I do
>apologize for my lack of Windows programming experience.

No apologies necessary. The creator of any software automatically
takes things for granted. <smile>

>When I ran startMDB.exe from my desktop, it worked fine. So, do I repeat the
>exact *same* steps for subsequent users (using their workstation), or is the
>process for second (and subsequent) user(s) different?

Not sure what you mean by exact "same" steps but I hope my explanation
above answers your questions.

Tony

Signature

Reply to this Message

Amit - 23 Jul 2005 02:42 GMT

Hi Tony,

I just read your response. THANK YOU!!!
I think you have cleared up all my questions. I will try out your
suggestions on Monday, and if it still doesn't work, then I'll re-port.

Have a nice weekend.

-Amit

> >I still have a couple of questions after reading your response, and
> >re-reading the pages on your auto-FE updater website. Will appreciate it if
[quoted text clipped - 51 lines]
>
> Tony

Reply to this Message

Amit - 23 Jul 2005 02:46 GMT

re-post :)

-amit

> >I still have a couple of questions after reading your response, and
> >re-reading the pages on your auto-FE updater website. Will appreciate it if
[quoted text clipped - 51 lines]
>
> Tony

Reply to this Message