Replies

Bill:

Have spent much happy time with Vermont Country Store. Another source I expect you might enjoy is http://www.lehmans.com[/url%5D , a Pennsylvania Dutch company specializing in “non-electric” stuff.

Happy browsing …

If you’re looking for an authentic Baked Bean Pot (glazed crockery) try http://www.waysidecountrystore.com

I’m not sure of the order, but would assume that since the install order for O97 and O2k is O97 1st, then O2k, uninstalling would be the reverse order … if it matters.

If I were doing this, I’d use the control panel uninstall (Add/Remove Programs) for O2k first, then Eraser2000 (CD1 and CD2 versions if applicable). Then I’d repeat the exercise for O97.

On Eraser2000, CD1 refers to the apps installed from CD1 (Access, Excel, Front Page, Powerpoint, Word) while CD2 would be stuff like Publisher and Photodraw.

Again … I’m not sure, but am surmising. Someone else may know for sure.

Microsoft has a downloadable Office cleanup utility (after uninstall) called Eraser2k.

They used to also have Eraser97.

I doubt that Charlotte is “fast”, but she sure is “quick”!

Usually refers to a quarter pound ( 4 ounces)

In “sorting and grouping” on the report design screen, group by state and sort by individuals?

Charlotte and Wendell:

Thanks … everything working correctly. Now when someone tries to open the back end on the server by double clicking the file, the “You don’t have the necessary permissions …” message.

I had been missing the obvious — Open the back end and secure the objects!

Thanks again,

Charlotte:

Thanks … will do. Have used the Sec Wiz this time. Now will split and secure back end, then copy to server location.

Wendell & Charlotte,

Thanks for the replies. Stayed out of the office Sat & Sun, but am back in today. My intention is to go back over all steps beginning with creating and joining the work group, making a new database, and importing all files including the backend data files. That way there’s no question about my being the “owner”, although the current fe security shows me as the owner. I work in a directory called “Shared”. The database and mdw files are in c:shared.

Full shortcut text is as follows: “c:program filesmicrosoft officeofficemsaccess.exe” c:sharedMitProj.mdb /wrkgrp c:sharedMitProj.mdw (My usual practice is to create the mdw file with the same name as the mdb file, which avoids confusing myself.)

Once the new db is split, is it necessary to reapply security separately to the backend? If so, this is probably what I’m missing. BTW I’ve tried the Security Wizard a few times, but don’t regularly use it since I thought I finally understood the security routine.

Thanks for the input … am off to rebuild the whole thing.

Thanks for trying. We seniors have to stick together.

Yes … and if I try to log in as admin with the assigned admin password I get the “You can’t get there because you don’t have the necessary permissions” message (or words to that effect!). You know the one I mean.

Hans:

Thanks for the suggested MSKB article link. Have got it working in one of my “secured” apps. I specified the backend (full path) in the “Data Source” code lines since it seemed to make sense that the backend was the part that had multiple simultaneous users.

Since this is a “normal” split situation (backend on the server / frontend and .mdw file on the workstations) I was surprised to find that it showed me logged in to the back end as ‘Admin’. I thought I had a pretty good understanding of Access Security, having worked with it for a few years. Now I guess I’m missing something. Security was handled before splitting the app. The normal make new workgroup file, join it, give Admin a password, create a new user (myself) in Admins Group, take Admin out of Admins, import everything to a new database under the new workgroup so I’m the “owner”, create necessary users and groups, assign permissions to the Groups depending on function, and take all permissions away from the Users group. Then the database gets split and the backend placed on the server.

Then a shortcut is created calling the appropriate security .mdw file, and I rejoin System.mdw (where all workstations are). The frontend mdb and the security mdw files are placed in a new directory on the workstations and linked to the server backend. The shortcut goes on the desktop.

Since Admin is now part of Users only and that group has NO permissions, how can Admin be showing up as logged at my workstation? When checking permissions, the linked backend tables show the proper group permissions (Admin has none!)

I guess my question is: If I need to provide additional security for the back end, how do I do it? My “bible” (MS Security FAQ) seems to have been leading me in circles today. Maybe someone can help. I’m probably missing something obvious and am over analyzing.

Thanks

Microsoft has a utility available for download called ‘Eraser2k’ which removes all traces of Office2k. They may also may still have one available for Office97 called (strangely enough!!) ‘Eraser97’.
I can never remember where they are, but go to the Access section and search for “Eraser”. Last time I downloaded them I kept copies in a temp directory, where I stash useful miscellaneous stuff, so it was available.

That’s interesting, Wendell. Went to your site and looked at AccessUI to get a better view.

Thanks,

Wendell:

Would you care to elaborate any on your “Taskbar” approach to providing menus for an app?

I have also avoided the “Switchboard” in past applications (mainly due to not really understanding its approach) in favor of forms and tabbed forms to avoid “button overload” for novice users.

Having said this, I find that Susan Novalis’ Access 2000 VBA Handbook makes an intriguing case for the switchboards as single forms with different characteristics depending on function.

I’m one of those people who have been “doing the job” for several years using necessary vba coding and some probably shameful workarounds but producing useful apps that work and don’t break. Now that I’m officially a senior citizen I’m getting back to learning some of the basics now.

Have really appreciated this forum for the last several years.