Stopping a macro (for others other than Primary users)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an update macro running on the Startup Form.

I need to have others use the DB but they have no access to certain files
that are imported with the Macro.

Does anyone know if the Conditions will help? or is there any other way.

I Have a Batch File that Does a FTP extract of Files from my MainFrame.

I import the File and Have it update our tables.

Any help is always appreciated,

-The Novice
 
SS,

I have a Single DB that One person is entering Vehicle Data as they come
into the Facility. They Validate PO's and Appointments. The Merchandising
Department Needs the tool to Validate if a PO has been completed and if the
Truck is still here or if it has left.

The Macro Reads a TXT File that is located in a local folder (I Found that
it Imports Faster than from the network). I have the Macro run on the Forms
Timer every 30 minutes.

Therefore if the Merchandising department was to open up the DB it will want
to run the macro.

I was wondering if I should use Conditions and if so(or not) what would you
recommend?

Thanks in advance,

Charles Davis
 
Charles,

Do you have a split database structure here, with the core data tables
in a backend mdb file on the server, and a separate copy of the
application file, containing forms etc, for each user on the local
machine? If not, then you absolutely should have.

There are various approaches you could take here. Use an API call to
identify the user logged in. If you are not doing frequent design
changes to the application, simply removing the macro from the
Merchandising dept's copy would be an efective hack. Otherwise, put a
simple table with one field, one record, and a form that pops up
whenever the application is opened, with an Option Group bound to this
table, where the user will select one option if Vehicle Validator, and
the other option if Merchandising or whatever, and then you could use
this value in the Condition of the macro... syntax would be something
like this...
DLookup("[YourValue]","YourTable")=1
 
Back
Top