I don't like the MDW file

[Anthony]

can anyone think of any alternatives to use instead of the MDW file?

In other wors, provide the same type of security in a dirfferent way,
withouth using the MDW file?

 

[Douglas J. Steele]

What sort of security are you looking for?

Access User-Level Security, which is probably what you're talking about when
you're saying MDW file, isn't that secure anyhow.

 

[Bill Mosca, MS Access MVP]

Anthony

You can build your own security by storing user names and passwords in a
hidden table, but that is even easier to crack than Access user level
security (MDW's). If you decide to do this, I suggest some code algorythm to
"encrypt" passwords.

Getting the user network name is simple. Use Environ("USERNAME"). From
there, you can show or hide forms/reports.

I noticed you posted this to several user groups. Cross-posting is
unnecessary and considered rude by many users. These groups are active
enough that one should get your questions answered within a reasonable time.

 

[Anthony]

If crossposting is rude then why does Microsoft Outlook Express allow it?

 

[John Vinson]

can anyone think of any alternatives to use instead of the MDW file?

In other wors, provide the same type of security in a dirfferent way,
withouth using the MDW file?

Probably, if you don't mind spending quite a few hours of difficult
and complex VBA programming to get a less-secure result.

Workgroup security is indeed complex and can be broken - but it's
complex because database security IS a complex task!

If your main concern is data security, you may want to consider
upsizing the database to use SQL/Server as the data storage medium.
SQL security is quite strong and not much more difficult to implement
than MDW.

Note that crossposting to every newsgroup under the sun is considered
impolite and will certainly NOT get you a good reputation (or probably
even a better answer); most of the volunteers here cover several
groups. A single post to m.p.a.security, or maybe crossposting to
m.p.access, would have been plenty.

John W. Vinson[MVP]

 

[Anthony]

If crossposting is rude then why does Microsoft Outlook Express allow it?

 

[Douglas J. Steele]

Outlook Express also allows you to post in HTML, and include attachments,
both of which are discouraged in most newsgroups. Just because a product
allows you to do something doesn't mean it should be done.

I think that the point Bill and John were trying to make is that you need to
be selective in your cross-posting. Some of the newsgroups to which you
cross-posted, such as conversion and externaldata, have nothing to do with
your topic.

 

[Bill Mosca, MS Access MVP]

Some users consider it rude because they monitor several groups and see the
exact same post over and over and have to mark them all as read. Can you see
how that couuld be annoying?

I'm not trying to teach manners. I just thought I should bring it to your
attention that it is unnecessary.

 

[Joseph Meehan]

can anyone think of any alternatives to use instead of the MDW file?

In other wors, provide the same type of security in a dirfferent way,
withouth using the MDW file?

What about the MDW file is the problem?

What exactly are you trying to accomplish?

I suggest that cross posting is not usually a great idea. It is usually
the signature of a SPAM artist. If you want to be taken seriously you
should try and avoid it.

 

[Rick Brandt]

Some users consider it rude because they monitor several groups and see the
exact same post over and over and have to mark them all as read. Can you see
how that couuld be annoying?

That would happen with Multiposting, not with Crossposting. Crossposting is only
frowned upon when the number of groups is excessive (which it was in this case).

 

[Rick Brandt]

What about the MDW file is the problem?

What exactly are you trying to accomplish?

I suggest that cross posting is not usually a great idea. It is usually
the signature of a SPAM artist. If you want to be taken seriously you should
try and avoid it.

Crossposting is fine and is actually preferred to multiposting as long as the
number of groups crossposted to is reasonable.

To the OP... The built in security provided by Access is complex because it has
to be to work. Anything you cook up yourself would be trivial to get through by
anyone having even a passing familiarity with how Access works.

If you want real security use a server database.

 

[Larry Linson]

If crossposting is rude then why does
Microsoft Outlook Express allow it?

Crossposting, with restraint, and with some thought to the applicability of
the groups, can be useful in some circumstances. That is why it is allowed.

In any circumstances, excessive crossposting is unnecessary and annoying to
the very people who can best answer your questions, as is arguing with them.
That is why every news reader has a capability to "killfile" or "twit
filter" so they won't be bothered with "twits."

In active newsgroups, such as these, any crossposting is excessive, and
certainly repeated demands for reasons that no one but the designers of the
software can know, such as the one quoted here are annoying to the people
who can help you. I suspect you have already earned the right of admission
to at least a few "killfiles" -- keep up what you are doing to get in more
and, soon, your posts will be deleted before anyone dowloads and reads them.
(This is not chastizing you, nor threatening you, it's just sound advice if
you want help in the newsgroups.)

For good suggestions on effective use of newsgroups, see the FAQ at
http://www.mvps.org/access/netiquette.htm..

Larry Linson
Microsoft Access MVP

 

[David W. Fenton]

I suggest that cross posting is not usually a great idea. It
is usually
the signature of a SPAM artist. If you want to be taken seriously
you should try and avoid it.

I kill any post crossposted to more than two newsgroups,
automatically, so most such crossposts I'd never see.

I suspect that the more expertise a reader of the newsgroup has, the
more likely he or she is to be killing on excessive crossposts.

 

[aaron.kempf]

yeah use SQL Server; it's 100 times more effective / secure.

you can use existing users / groups.
it works like a charm.. and it doesn't take extra maintenance.

System.MDW is a maintenance nightmare

-Aaron

 

[Guest]

can anyone think of any alternatives to use instead of the MDW file?

In other wors, provide the same type of security in a dirfferent way,
withouth using the MDW file?