Open another databse from current access databse

[Cpreston]

Hi

I simply want to open another access database from a form within another access database.
Is there a way to do this without complex coding using a button.

Thanks

 

[Cpreston]

Managed to do this through hyperlink.

How do I get rid of the Microsoft Access Security notice from popping up each time I sue the button please.

thanks

 

[MajP]

Do you really need to open the other database or do you want to exchange data with the other database? Can you explain a little more what you want to do with the other DB?

 

[Cpreston]

The other database runs various qry's and updates and creates CSV files through a module and a form that loads automatically.

This then stays on screen and waits for new files to run the module again , however, keeping this database open all the time is taking up memory and freezes the main database. If we then close the database that runs the module the main DB keeps forze and in the end we have to restart the computer completely.

The person who developed the DB says both DB have to be open all the time, but from what I see it only needs to be open to run the module and then needs to be closed down so it free's up memory to prevent the main DB freezing.

So my though was to have a button on the main form to open the database, let it run the module, take out the waiting function and have an shut down button on the module database to close it correctly

Hope that explains it briefly

Thanks

 

[1DMF]

How do I get rid of the Microsoft Access Security notice from popping up each time I sue the button please.

If it's about not being trusted then you need to use Trusted Locations.

I do this via a reg key

[HKEY_CURRENT_USER\Software\Microsoft\Office\[highlight #FCE94F]14.0[/highlight]\Access\Security\Trusted Locations\Location[highlight #FCE94F]1[/highlight]]
"Date"="[highlight #FCE94F]01.01.2014 00:00:00[/highlight]"
"Description"="[highlight #FCE94F]Your Application Description[/highlight]"
"Path"="[highlight #FCE94F]C:\\PATH_OF_ACCESS_APPLICATION_DIRECTORY\\[/highlight]"
"AllowSubfolders"=dword:00000001

You need to amend the highlighted bits to reflect your environment

14.0 = Access 2010 (All my users run my apps via Access 2010 Runtime so one reg_key fits all)
Location1 = Location ID (Use a Location number that is free : Location1, Location2 etc..)

View your current Trusted Locations entries (via regedit) to see what (if any) are being used.

As always when messing with the windows registry - back it up and be careful!

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music

 

[Cpreston]

Hi

I tried this and restarted the computer but still have the same message come up. Attached is how my regedit looks, think it is correct though but could be wrong

Thanks

 

[1DMF]

Can you provide a screen shot of the message. This only works if it is the untrusted message as mentioned.

You state you are using a hyperlink, if you mean the FollowHyperlink warning, this won't resolve that.

That warning is endemic of using this method, to stop it appearing you need to use an alternative method for opening the DB.

Have a look here :

http://www.utteraccess.com/wiki/index.php/Opening_Files_From_Access

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music

 

[MajP]

The other database runs various qry's and updates and creates CSV files through a module and a form that loads automatically

If it was me, I would not design it this way. I think this is just asking for problems. Simply link to the tables in the other database. Import the queries, forms, and necessary modules and run it all from the main DB. Seems like a ten minute solution to me, and way more efficient.
Alternate solution would be to add the second db as a reference to the first, giving full access to the second DB.

 

[1DMF]

^agree, helping you with your particular question, is not indication that it is the right way to do it ;-)

"In complete darkness we are all the same, it is only our knowledge and wisdom that separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Free Electronic Dance Music