New version of the Auto FE Updater

[Tony Toews [MVP]]

- Windows Vista now supported.
- Starting an exe, such as the Sagekey runtime system, is now supported.
- Fixed the "The MDW account name and password in the INI file weren't valid for
opening the MDB to determine the version of the MDB" message when in a mixed
operating system work station environment.
- Emphasized using %appdata% as a location for the Front End MDB/MDE in the sample
ini files and documentation
- d error numbers to the messages. It was getting a bit difficult tracking down
specific error messages in the code.

http://www.granite.ab.ca/access/autofe.htm
--
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/

 

[David W. Fenton]

- Fixed the "The MDW account name and password in the INI file
weren't valid for opening the MDB to determine the version of the
MDB" message when in a mixed operating system work station
environment.

Can you share the solution on that one? It was a real stumper for
you at one point, no?

 

[Tony Toews [MVP]]

Can you share the solution on that one? It was a real stumper for
you at one point, no?

Ahhh, it is so embarrassing I don't want to even mention it. There
was a difference in the crypto API settings when creating the initial
hashing value which was updated on the INI file compared to the crypto
API value when I decrypted the hash value.

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/

 

[David W. Fenton]

Ahhh, it is so embarrassing I don't want to even mention it.
There was a difference in the crypto API settings when creating
the initial hashing value which was updated on the INI file
compared to the crypto API value when I decrypted the hash value.

Don't be embarrassed! We all make mistakes like that, and they are
often the hardest to find.

Thanks for maintaining the thing -- it's awfully useful and
impresses my clients no end whenever I introduce them to it (I don't
take credit for it, just for knowing about it!).

 

[Tony Toews [MVP]]

Thanks for maintaining the thing --

You're quite welcome.

it's awfully useful and
impresses my clients no end whenever I introduce them to it (I don't
take credit for it, just for knowing about it!).

It was rather amusing visiting a new client several years ago. I
started to explain some things about split databases and such. They
interrupted with some questions. I had all the answers immediately at
hand which I was going to explain anyhow.

At the end they looked at each other and said "Sure looks like you
know what you're doing." <smile>

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/