Search results

Bob: Actually I resolved this last night. With the Macro that I'm using to run the code, I just added another line to it with the command "Quit". Everything seems to be working great now! Thank you again for your speedy response and help with this. JB

I can't seem to get "DoCmd Quit" to work at the end, or "acc.CloseCurrentDb". Any thoughts on this? JB

I have some code here that works fine as far as opening up a second database. The problem I seem to be running into now is when I close the original Db, the new database I just opened closes too. Any ideas out there on how I might add some code to this? My goal is to have this code in a form...

Code that I have the works for this close is: *****Code Start***** Dim ObjAccess As Access.Application Set ObjAccess = GetObject(""File Path Name") ObjAccess.CloseCurrentDatabase ObjAccess.Quit *****Code End***** My problem is that if I accidently hit this button when the other database...

I want to be able to close one access database by using another. I did have some code that involved the "GetObject("FilePathName") command, and it worked but of course I didn't save it and I managed to lose it :( What I'm looking for is a code that when I have it attached to a button on a form...

I took out the line to run the macro to see if I can get just the file to open first. I just put the code in a .vbs file and it did the exact same thing when I ran it (Open and closed immediately). Let me know if you have any luck with this. Thanks. JB

Would it still work the same if I put this in a module in another Access file? I got it where the window opens but then closes immediately after. Here is the code I have, any help why you think it might not be working would be greatly appreciated. **********Code Start********** Option Compare...

Where would you normally insert this code? On a form with a button, marco...? I can't seem to get the window to stay visible, it still closes imediately, do I need to change my reference? JB

You can find the password through some of the code, but you can also lock the code out too.

Ironically I did spend a lot of time combing through these examples yesterday. Just still hazy on it as I'm new to a lot of these topics. JB

I like the sounds of the first part talking about opening up the secured database in another runtime instance. I'm just still hazy on how to go about it. Am I just creating a VB file, and then on click it runs or what? I didn't understand this part from alancossey: VB6 code to open Access OK...

I'm pretty sure that the Users are savy enough to look at the back end by linking or importing, and also viewing system objects. I'm pretty confident they wouldn't know where to look as far as passwords are concerned though.

A password would protect the objects from being linked to. That is the purpose I am trying to get here. It looks like I'm just at a dead end and Access is really limited as far as security is concerned.

I would have to enter this code in for every query? Couldn't this still be viewed if I just checked the view "Hidden" objects from a blank database when trying to link to this one I'm trying to hide the queries in? JB

Is there a way of Password protecting an Access 2007 database automatically through VBA? This is going to sound funny but I am pretty sure if this will work then I might have it fairly secure. I'm looking for code that will diable the password on open and set the password on close. Is this...

I usually keep it off. For the sake of these examples it was on, so sorry to get your worked up over that j/k. Do you have an idea or answer to my question on how to hide queries or objects from being viewed by linking or importing to my databases? JB

Well I don't have to change anything in the forms since the "Auto Name Tracker" is turned on. I would just have to change the names in the VBA code so that these could run. Is there a way to hide object through code where other users couldn't link to it from a blank database? I'm working...

I liked your "hide queries" code very much. However, I'm running into the problem now, I have a form with buttons that I use to run queries to generate reports. It seems now that the code for these buttons can't locate the query. Any ideas on how to correct this? JB

I was lead to believe that splitting a database pretty much ment you could hide the tables and not queries. Am I incorrect about this? JB

There is a way to protect Modules from being viewed in Access 2007, is there a way to do this with other objects as well? JB