Opening a database?

[wh00t]

Here's a little problem I have and wondered if anyone knows a way around it.

I currently have many databases that I have created for work and they are quite happy running away doing what they are meant to do on a 2000/NT setup, we will soon be switching to our parent company's network 2003/XP/Citrix which is presenting me with the following problem and we do not have any control over how this is run.

We can no longer create desktop shortcuts to the databases as current, they will place 1 database in the start menu and would like this to be used as the database menu so that all databases are launched from this.

So I am trying to launch access databases from within an access database (Access XP), here's what I have tried so far

Shell - works when I use full MS Access but does not work in Run Time versio n which is what the users will access, shows no error, it just beeps and does nothing.

SendKeys - %fo<FileName>.mdb~ - again works in full access but not in Run Time as RT does not have 'open' in the file menu.

FollowHyperlink - this actually works but I can not get this to open the new database as a full screen window, this requires the user to either run everything maximized (not ideal as some forms are designed to run side by side) or for them to resize the main forms.

Are there any other ways to open a database from within access RT version that will open the access application full screen?

 

[ByteMyzer]

Try this:

Public Function OpenDb(dbPath As String)

    Shell """" & SysCmd(acSysCmdAccessDir) _
        & "MSACCESS.EXE"" """ & dbPath & """", vbMaximizedFocus

End Function

Then call the code with something like:

OpenDb "C:\MyDatabase.mdb"

See if this works for you

 

[The_Doc_Man]

1. Consider consolidating the multiple little databases and build a switchboard that shows you things users can see. Don't let them see "reality" (i.e. the table, query, form, report, etc. panes).

2. Beware of using CITRIX. This might work but may be a technical violation of the Access license because it would be a case of multiple users opening the database at the same time. Your Access license, assuming you bought it "over the counter" at any of several retailers (Office Max, Best Buy, CompUSA, or equivalent), is a SINGLE USER license.

 

[CraigDolphin]

2. Beware of using CITRIX.

Never a truer word was spoken. I believe the makers of Advil are secretly behind the push for Citrix deployment.

 

[wh00t]

As said, I have absolutley no say / control over this, the lisence is not a problem as we use the developers edition and all users access databases using the run time version.

I can't consolidate the databases, some of them are not little so would not all fit a 1 database, all tables / queries / anything remotley design type are locked when using run time version automatically.

ByteMyzer - thanks but this still gives me the same 'beep and do nothing' of the other shell command I tried.

 

[The_Doc_Man]

I return to the idea of a switchboard form. Maybe it is the only thing that is in the database you open at first.

Behind each "button" on the switchboard, you can run code that opens a given database in your workspace. You can then access the items in the Documents collection of that opened database. (NOTE: A closed form is a document. It isn't in the Forms collection until it is open. Same logic applies to reports.)

There is no reason you couldn't run multi-layered or tab-controlled forms as part of your switchboard, in which case you would have a lost-focus event for the form or tab that would give you the chance to close the secondary database and open something else if needed.

I cannot emphasize strongly enough that is a VERY complex road you walk. You say you have no control. But you do. Try to estimate how long it would take you to do this. Figure out the monetary cost of your time. Then tell the boss - I can do it for X dollars/euros/pounds/lira. It costs you Y dollars/euros/pounds/lira to buy copies of Access for everyone. If y < x, you have regained control.