Search results

I didn't quite understand this way. Just setting the dirty property to false forces the form to be saved and show the changes in the listbox?

dcrake the solution you provided worked like a charm. But I'm now facing the same problem with the Save command. What's more although you can perform the delete action with a delete query I can not think of any corresponding query for the save command. Maybe properly constructing an Append...

It works, thanks!

To the best of my knowledge this process won't transfer the relationships though. Do we have to recreate them or is any other automatic way?

I have a secured database with one admin account PAdmin1, who is the owner of the database. Let's call the mdw file associated with this database sec1.mdw What I want to do is to transfer the ownership to an other account, PAdmin2, which is defined by a second security file sec2.mdw. The...

thanks a lot dcrake

Yes, forgot to mention it. No result.

I have a Customers table containing all my Customers personal data and a Form frmCustomers for handling them. At the Form there's a listbox displaying all the Clients (fullnames) for quick access. I delete the current record in my Form by calling the VB command DoCmd.RunCommand...

Ok, start it all over and do it totally manually. I am convinced that problem occurred due to the fact that on some step of the previous guide the security setting are actually applied to the system.mdw file instead of the custom one. That's the reason why removing the custom mdw the DB still...

Do you find anything wrong to the following steps? 1. You may secure any database that has been created while joined to the System.Mdw. 2. Create a new workgroup file(*. MDW) 3. Open the unsecured database and create a password for the Admin user. 4. Create a new user account that...

Already did that. Yes it can be done, but only after deleting the mdw file.

Did both This is what I didn't do. May this be the cause? I'll give it a try and post back. When you say all you mean also the custom Admin account I created?

I'm describing the situation and the problem I'm facing at first post. As I'm writing there, the problem is that if I delete the mdw file then the DB starts to the default state with full permissions. I suppose I'm failing in binding the mdw file with the mdb.

I think I spotted the problem. Something goes wrong with step 8 in the tutorial I've posted at first post. If I run the security wizard to the unsecured mdb and choose create a new workgroup file, db is properly secured. If I do it as the tutorial describes, i.e. manually creating the mdw file...

I have secured my mdb following step by step the below guide http://www.moretools.com/lessons/access_security.htm I changed the owner of mdb from the default to one I created, and also removed the default admin account. I tested all the permissions and the seem to work. Then just for testing...

Thanks a lot of your advice. I've already begun studying about and trying to get the best of. I've read that user groups have been removed from Access 2007. Since I don't have it at my disposal to try it, I'd like to ask if it is true. And if that's the case, is it possible to migrate the DB...

If I understand well you have a login system, in other words an input box appears when anyone opens the DB, and according to the username/password provided he/she granted with the right priviliges. If that's the case, I'm afraid it is not what I'm looking for because I don't want to make simple...

Oh, I just figure out that ghudson's code permanently hides the Access menus globally (to all Access DB's even new ones)! This makes things more complicated...

After a year of work I've almost finished the development of a database (DB) in Access 2003. Before sending it to the purchases I reasonably want to secure my work. My ultimate goal is 1) to have a DB split in FrontEnd and BackEnd stored both locally at user's PC 2) user to have no special...

I don't think so. As I said previously I can call the same function from other functions/subs without providing the (optional) argument. Problem occurs only when trying to call by directly declaring it at the button properties