Search results

  1. P

    Hiding Access

    Hiding Access (application disappears!) Well, I can get the first window to minimize appropriately, but clicking on buttons to go to other forms seems to make the entire application disappear. Occasionally, when I load the application, the whole application disappears as well (no minimizing or...
  2. P

    Unsecure Backend After Splitting

    Thanks Jeff for the advice - I had started wondering if I should just run the user level security wizard again for the backend, thus "resecuring" the database. But I am worried about the front end then needed a second password or having issues connecting to the backend. I'll need someone to...
  3. P

    Unsecure Backend After Splitting

    Help - Backend Unsecure after split So I split my database and turned the front end into an MDE for final deployment (or at least version 1.0). After playing around with it today, I noticed that the front end is secured but the back end is not. The front end can only be opened by its...
  4. P

    Secured Workgroup Default Setting

    BTW - Thanks for the advice on the shortcuts. I've implemented them, and everything is working great now (I don't have to manually switch Workgroups through the Access Window). I still am at a loss as to why my backend would lose it's security though.
  5. P

    Secured Workgroup Default Setting

    Right - I found the problem that I was joining into the system.mdw. My main concern now though is that after splitting my database, the backend will allow any workgroup to access it - even after joining the correct one, you can still switch to system.mdw and access it. How do I lock this down...
  6. P

    Secured Workgroup Default Setting

    Okay - I found the reason it was having problems. However, in the process I also found that after splitting my database, the back end will accept any workgroup you assign to it! The front end is properly secured and will only function with the workgroup it was assigned to, but the backend is...
  7. P

    Secured Workgroup Default Setting

    BE Security gone after split Help! Every database I open, from unsecured databases to new databases, is now opening with the secured workgroup file that I set for a secure database. It means I have to type in my login information for every database? How can I stop this from happening? I want...
  8. P

    Removing user level security

    Found it, thanks for the heads up - it's a treasure trove of security info. I'm assuming that the document applies to Access 2002 also, even though it's creation date was in 2000. Thanks again - Pat
  9. P

    Removing user level security

    Just curious - I have all the passwords, etc for my workgroup, but at some point I will need to remove the user level security from the database so it can open will full access to everyone (no user/password login) What is the easiest method to doing this? Im running Windows XP and Access 2002...
  10. P

    Access enquiries - what is their worth?

    I would also be very interested in this - I've just put together a database that we want to resell, but don't know what a ballpark figure would be (it's a specialized database with specific forms for a small field of people). What would you charge for a mid-size database complete with forms...
  11. P

    [OFF TOPIC] Happy Holidays

    Happy Holidays (off topic but thanks!) Just wanted to thank everyone here and wish everyone a happy holiday season. The help provided by this forum was essential for my latest access project's completion. Thank you all again and happy holidays!
  12. P

    Default Workgroup file

    When I distributed my MDE FrontEnd, I had to repoint them all to the secured.mdw on the network. Is there a way to hardcode the directory as "F:\etc...." so it does not default to the directory that it is copied to? It would just be nice for future distributions. Thanks :)
  13. P

    Making an MDE

    Excellent - worked like a charm :)
  14. P

    Making an MDE

    Almost finished, making the MDE? Okay, everyone here has been SO helpful getting everything set. I've got a nice database, with workgroup security deployed on it for user level access. The database is split and the backend is on the network drive, while the front end resides on the user system...
  15. P

    Hiding Database Window

    I did search for that option - but it only seems to allow a checkmark when the startup form is set to "none". There is an option "Startup Database Window" which is unchecked. Thanks for the assist, Pat
  16. P

    Hiding Database Window

    Hiding Database Window (program look) Is there a way to hide the database window and have it open to a default form in the Startup options (none programatically?). We are all running WinXP and Access 2002 SP2 Thanks, Pat
  17. P

    Updating forms in MDE, but retain data

    Once I deploy the MDE, is there an easy way to get everyone's current Secured shortcuts to point to the MDE? Or will I have to resetup workgroup security for the MDE. Currently, everyone has a shortcut that points to Secured.mdw and is the workgroup security file for the MDB. Thanks again for...
  18. P

    Updating forms in MDE, but retain data

    Wayne, thanks for the assist. I do want to split the database, which would solve a lot of my questions. I had a question in another thread, maybe you can answer it? Just wondering if there's anything I should know ahead of time about splitting a database that has Workgroup security (i.e. is...
  19. P

    Updating forms in MDE, but retain data

    Thanks for the quick reply - by "dropping" the tables out of the MDE, do you mean exporting? Or is there a special "dropping" method? Thanks again, Pat
  20. P

    Compact ReadOnly Error

    Exactly, same here - I had to switch off Compact on Close because users were getting the error randomly and not knowing how to rename/get around the message. Major headaches - we are all on SP2 Access 2002/Windows XP
Back
Top Bottom