Auto FE Updater

Hi

I'm attempting to use Tony Toews utility. I've set it up after taking
awhile to figure it out (this is due to my inexperience and definitely
not the utility!) I'm not sure if I've done this right but I have
an .ini setting for each user, which sets each users "my documents"
folder with their front end, sets the short cut up, I've then
subsequently hidden their FE folder and it successfully checks for a
latest FE from a central shared folder and pulls this across if so
before opening the FE. The guidance talks about only 1 .ini file but
as mentioned I've set one for each user- I couldn't understand how
only 1 could work.

Anyway, the problem I'm having is that i can only open up the
StartMdb.exe file from the specific PC that I extracted the file to
initially, eventhough the folder is in a shared location. I get the
message:

1042 - Null command line sent to utility.

If you are using a shortcut the target in the shortcut hasn't been
properly setup.
If you are using a bat or cmd file then the line calling this utility
hasn't been properly setup.
It should be in the following format:
StartMDB.exe /cmd /inifile:"z:\test\ini file name.ini"
or
StartMDB.exe /cmd /inifile:"\\server\sharename\ini file name.ini"

When I try to open it on other PCs linked to the network. I've tried
looking at system settings and the file doesn't seem to have set any
local registry settings on he specfic PC. I've overwritten the file
using an extraction from an admin console login on another PC but
still it only works on that specific PC!! My admin has also tried
running it through a batch file command using the recommended path
advised in the problem diaglogue.

So, the utility is great and works fine but I can only access it from
1 specfic PC on the whole network. Any advice is greatly
appreciated.

many thanks

David

Re: Auto FE Updater

On Jan 28, 11:34=A0am, David wrote:
> Hi
>
> I'm attempting to use Tony Toews utility. =A0I've set it up after taking
> awhile to figure it out (this is due to my inexperience and definitely
> not the utility!) =A0I'm not sure if I've done this right but I have
> an .ini setting for each user, which sets each users "my documents"
> folder with their front end, sets the short cut up, I've then
> subsequently hidden their FE folder and it successfully checks for a
> latest FE from a central shared folder and pulls this across if so
> before opening the FE. =A0The guidance talks about only 1 .ini file but
> as mentioned I've set one for each user- I couldn't understand how
> only 1 could work.
>
> Anyway, the problem I'm having is that i can only open up the
> StartMdb.exe file from the specific PC that I extracted the file to
> initially, eventhough the folder is in a shared location. =A0I get the
> message:
>
> 1042 - =A0Null command line sent to utility.
>
> If you are using a shortcut the target in the shortcut hasn't been
> properly setup.
> If you are using a bat or cmd file then the line calling this utility
> hasn't been properly setup.
> It should be in the following format:
> StartMDB.exe /cmd /inifile:"z:\test\ini file name.ini"
> =A0 =A0 or
> StartMDB.exe /cmd /inifile:"\\server\sharename\ini file name.ini"
>
> When I try to open it on other PCs linked to the network. =A0I've tried
> looking at system settings and the file doesn't seem to have set any
> local registry settings on he specfic PC. =A0I've overwritten the file
> using an extraction from an admin console login on another PC but
> still it only works on that specific PC!! =A0My admin has also tried
> running it through a batch file command using the recommended path
> advised in the problem diaglogue.
>
> So, the utility is great and works fine but I can only access it from
> 1 specfic PC on the whole network. =A0 Any advice is greatly
> appreciated.
>
> many thanks
>
> David

Update on Auto Updater!

In case anyone is following this. I've moved the startmdb.exe
shortcut into a different folder, tried to access it on a different
workstation PC and got the following message:

"A master entry was not found or was empty in the AutoFEUpdater.INI
file."

So now I've worked out that this ini is the one used to assign PC
workstations at start up of the utility- I don't think it mentions
this in the guidance! I guess the idea is just to limit access to the
console from a single central admin workstation, but that doesn't suit
my needs- I would rather set up for mutiple entry points and then hide
the folder. I guess I'm doing this all in a bit of a 'quirky' way.

Also, I've noticed that when you run the updater for the first time
from a user shortcut after you have set up the local FE and hidden the
folder, it brings up an error message but carries on to open the
Access FE. This only happens once and then is fine. I guess this is
to do with hiding the folder and files initially?

Anyway- feel free to comment if anyone is keeping up, and thanks to
Tony for the utility- very helpful indeed.

thanks

David