Auto FE Updater Tony Toews Error Message

[Craig]

Hello,

I am using Tony Toews' Auto FE Updater version 1.74 to update the front end
of an HR-related database. At first, I was using this for employees solely
within an HR department, and it did exactly what I wanted it to do and worked
great.

Then I began slowly distributing it to individuals who were not within the
HR dept., and almost all of them began getting this error:

1018 - The following problem occurred in routine 'FindMatchingMSAccessEXE'
Type mismatch

The only thing I can think of to distinguish users within the dept. and
users without is that users within have (Windows network) permission to read
& execute, list folder contents, read, and write, whereas users not in the
dept. only have permission to read & execute, list folder contents, and read.

Would this make a difference?

Any help (from anyone with experience using Auto FE Updater) would be great!

Thanks again,

Craig

 

[boblarson]

To use an Access database ALL users need Read/Write/Delete permissions on the
applicable folder.
--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com

__________________________________

 

[Craig]

Thanks for the help --- I know that was probably a silly oversight on my
part. I worked with our I.T. department to set everyone up that way and it
seems to be working smoothly now.

Thanks again,
Craig

 

[boblarson]

Glad we could help!
--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com

__________________________________

 

[aaron.kempf]

I don't think that you should be using HR data with Microsoft Access.

sorry-- MDB or ACCDB isn't secure enough for a simple password brute
force attack.

When I worked at Microsoft-- we had _THOUSANDS_ of outbreaks a day.

Don't think for a second-- that _ANYONE_ has _ANY_ measure of security
_ANYWHERE_.

Sorry-- Keep your mission critical-- personnel or business data- in
SQL Server.

unless you don't give a hoot about privacy that is.

PS - is everyone goign to like it when they can open the DB; bypass
the password and determine who makes _WHAT_ money?

Honestly

get a clue; and hire someone on CraigsList to move your db to SQL
Server.

-Aaron

 

[boblarson]

unless you don't give a hoot about privacy that is.
Aaron: Why do you post with such negativity? Do you have some sort of
grudge or pain from childhood? Every post I have see of yours today seems to
have the same negative tone.

Putting information in an HR database isn't in itself insecure. If it is in
a location where only those who should be seeing the data can access via
network restrictions, then it is not really all that insecure. Agreed, if it
is on a public share that is accessed via other departments, etc. then it
would be highly susceptible. But the OP never mentioned it either way and
yet you took the most negative tone you possibly could.

Lighten up Francis...(obscure reference to the movie "Stripes" with Bill
Murray) You don't have to constantly attack others.

--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com

__________________________________

 

[aaron.kempf]

Stripes is a fab movie.

I don't have an attitude problem.
I have a crappy database problem.

Having sensitive data- is there _ANY_ HR data that isn't sensitive--
in an INSECURE database is just asking for trouble.
SQL Server is _EASIER_ cheaper, better, faster-- more reliable.

And it is _SECURE_.

There is no point to using an aboslete database.
What are you going to do when it goes corrupt? Blame the network?
Blame the users? Blame the design?

Sorry-- I blame the database.

Privacy of HR data is not something to be taken lightly.

-Aaron

 

[aaron.kempf]

Uh.. I just don't have a clue-- why you can't see the problem here.
It is a blatant oxymoron.
------------------------------------------------------------------------
To use an Access database ALL users need Read/Write/Delete permissions
on the
applicable folder.

 

[Alan]

Stripes is a fab movie.

I don't have an attitude problem.
I have a crappy database problem.

Having sensitive data- is there _ANY_ HR data that isn't sensitive--
in an INSECURE database is just asking for trouble.
SQL Server is _EASIER_ cheaper, better, faster-- more reliable.

And it is _SECURE_.

There is no point to using an aboslete database.
What are you going to do when it goescorrupt? Blame the network?
Blame the users? Blame the design?

Sorry-- I blame the database.

Privacy of HR data is not something to be taken lightly.

-Aaron








- Show quoted text -

Hi,

I don't know about other kinds of database. But if the Access database
really corrupt, you may try Advanced Access Repair at http://www.datanumen.com/aar/
This tool is rather useful in salvaging damaged Access MDB files.

Alan

 

[Tony Toews [MVP]]

On Apr 9, 2:15 pm,

You are replying to a posting that is over a month old.

I don't know about other kinds of database. But if the Access database
really corrupt, you may try Advanced Access Repair at http://www.datanumen.com/aar/
This tool is rather useful in salvaging damaged Access MDB files.

You also work for that company. Posting without disclosing any
connection is highly unethical.

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/