User Level Security Wizard 2000

[JustSara]

I went through the User Level Security Wizard and set permissions for everything (I'd give anything to go back and undo that). Everything I've read has said that you can't undo that but that you can go in and change the setting so that everyone has all permissions.

My problem is that I want to move my database (base.mdb) from my computer to the server. Base.mdb moves over ok and I can open the database from my personal computer but when I try to open it from the website it tell me that I don't have the necessary permissions. If I create a new database and name it base.mdb and put it on my server the web page opens up great. It's something to do with those $#&%#$ permissions.

I've tried creating a new database and importing everything over but when I do that I keep getting Expression Errors and I can't get in to fix it because it tells me that the network connection has been lost. Um... it hasn't.

Any help would be appreciated.
Sara

 

[uscitizen]

I'd gather you're in a situation that I could be in if I pursue this security angle some more. I'm in the process of wrapping up a database on my personal PC and would seek to move it on up to a shared file on our corporate server. I'm at the point where I think most (if not all) of the tables, forms, queries and reports needed are out of the way and have been developed and given a 'test' (by just me). The next step is to 'pilot' it and let a small group (half a dozen or so or less) users work with it on the server so I'm a looking at how to incorporate a modicum of security. What I'm reading in the MS Access help documentation is that there are conditions where just a database password is sufficient. At this point, I'm looking into what's involved if and when I were to decide to take it to the next level, i.e. 'security account passwords'. My users are not likely to want or know how to make changes to the design of the database, however if I were to take the simpler route (i.e. just assign a database password w/o also incorporating the security account passwords) I would nevertheless prefer to deny them the ability to view anything about the database except the customized switchboard/menu system I prepared. My thinking is that perhaps a strategy involving blanking (hiding) the tables, reports, queries, etc. using the MS Access 'hide' feature would be a possible strategy.