Start up options

  • Thread starter Thread starter Hafeez Esmail
  • Start date Start date
H

Hafeez Esmail

I have one database and two jobs. All they have in common
is that they use tblMasterList

Job 1:
Database to open by itself, run a few queries, run some
code and then close off when it's finished

Job 2:
Database to open right to a form, click a few check boxes
press a button (to create,export and then delete
qryCustomMade). Will close the databse manually.

Is it possible to create two shortcuts, one for each job?

Any help on this matter would be appreciated!
Hafeez Esmail
 
Hafeez,

I'm not sure it can be done. I can propose an alternative,
though, which in myu humble opinion is a neater solution:
break it down to a common back ned and two separate front
ends fro the two jobs. That is, keep your tables (just the
shared ones between the two jobs, or all of them) in one
database with nothing else in it (back end), and create
one front end (separate database) for each job, with all
the queries, forms, macros, code etc. for the job and
links to the tables in the back end. That way you can make
each do its job the way you want it, completely
independently from the other in every respect other than
the shared data.

Nikos
 
Second thoughts, if you don't want to go the FE/BE way:

If the two jobs are always performed by identifiable
different users (that is on different PCs oir with a
different LAN login name or a different user name in your
database), then you can use some code to determine which
of the two jobs to perform depending on the user (not a
very neat solution, if you ask me...)

The easiest way is to use a startup form with just two
command buttons, each of which runs one job. Sometimes the
obvious is the last one to think of!

Nikos
 
I'm always open to alternatives (especially neater ones :))

Here's the structure of my DB.
3 linked tables ODBC tables
I combine fields in these three tables to get tblMain
This table gets updated everytime qryMkTblMain is run
(make table query). Since this is the main table, both
jobs will need to access data from it, however the Make
table query will create a new Local table instead of
updating the Backend table.
Is there an easy way of dealing with this?

Hafeez Esmail
 
You can put the two shortcuts on your desktop

Macro - Run a macro from Sortcut
"C:\PathToAccess\Msaccess.exe" "C:\PathToDB\MyDB.mdb" /x
macroname

Jim
 
Back
Top