Re: Job Appraisal database setup

Tech-Archive recommends: Speed Up your PC by fixing your registry

Regarding USING the data (reports, summaries etc.) I think that an Access
front end would let you do a lot more with a lot less work / learning curves.


Regarding inputting the data, I guess "security" coverst two categories:

Limiting access to confidential / managerial data while still giving access
for input. I think that this can be done with either front end

Security from hackers and other ill intentioned people. I'd have to plead
ignorance on this one.

Sincerely,

Fred








"ngan" wrote:

Thanks to everyone for their opinions. I'll take them into consideration. I
am leaning towards the simpler solution because it isn't really mission
critical data.

What about the issue with having the FE in Access vs website (simple asp) in
regards to security?

"Fred" wrote:

Nothing cut and dry; I gave you my best guess before which was leaning
towards the simpler giant table method.

One new question is to what extent you are comfortable with understanding
and implementing the solution that Steve recommended. And, if anyone
besides you is going to be involved in maintaining it. the same question for
them.








"ngan" wrote:

Is there a litmus test to figure out which would fit my situation better?

"Fred" wrote:

Hello Nquan

One or two notes on your question on my response.

99% of databases using over 255 fields need those because they are
mis-designed. But 99% isn't 100%.

The simplicity vs. sophistication question at each level of use is always a
question. (it comes to this only when both choices are sound) The answer
should be dictated by your situation. I've been running small (20-50
person) technical companies for 26 years (getting deeper in on databases is
my hobby/indulgence) and so I tend to be more biased towards "simple". The
other extreme is that some designers like it to be so complicated and poorly
documented that they are the only person who can touch it. Or, there are
folks who, because they are fully immersed in a technology to the point of
seeing "simple" as boring, and see sophistication as a goal rather than a
means to an end. But, again, this should be decided based on your particular
situation.

.

Relevant Pages

  • Re: Pervasive SQL Help
    ... Security is implemented on a database-by-database basis, ... security from the databases. ... Post titled Pervasive SQL 9.5 Security Problems, ... "DBA" for a retail chain with 350+ stores, each of which had a PSQL ...
    (comp.databases.btrieve)
  • Re: How to remove Security from Access 2002
    ... Just back in the office today, your advice worked perfectly, thanks very ... databases, and vba but not much more advanced than that. ... "Joan Wild" wrote: ... Open Access and go to Tools, Security, Workgroup ...
    (microsoft.public.access.security)
  • Re: How to remove Security from Access 2002
    ... However, since you are joined by default to your secure mdw, that is what ... set up on my home MS Access databases so this one should be ... Open Access and go to Tools, Security, Workgroup ... Rejoin the standard system.mdw workgroup file. ...
    (microsoft.public.access.security)
  • Re: How to remove Security from Access 2002
    ... If you want a book entirely on Access security, Real World Microsoft Access ... data manager like myself who knows about databases, ... "Joan Wild" wrote: ...
    (microsoft.public.access.security)
  • Re: Job Appraisal database setup
    ... am leaning towards the simpler solution because it isn't really mission ... critical data. ... The simplicity vs. sophistication question at each level of use is always a ... person) technical companies for 26 years (getting deeper in on databases is ...
    (microsoft.public.access.tablesdbdesign)