Gary,
First, no, it can't be done via the table itself. Second, I guess I need a
bit more information about what you want to do. Are you saying that if a
user enters a value that exceeds your target value you want Access to shut
down? Do you want to give the user the opportunity to correct that value
before you injudiciously boot them out of the database?
Hehe! I am NOT that frivolous. I should have explained my reason for booting
people out though.
I have an application and I want the application to expire based upon an
event that happens in the processing. You could look at it and say, after X
uses the application will NOT run.
I want to ensure I get paid. This WILL all be spelled out in the EULA and
Contract... but one can't be too careful.
So no, I want the user to get a pop-up saying Problem, Contact Developer and
a phone number. And then acquiescence.
A usage table would hold a count; a macro could be used to Quit if the count
exceeds a certain criteria. I just can't seem to tie the two together in my
head.
Aha, so you want to provide demo copies of your application and have it
become unworkable after a certain number or runs or something like that. Let
me recommend that you take a look at Tony Toews' website:
Aha, so you want to provide demo copies of your application and have it
become unworkable after a certain number or runs or something like that.
Let
me recommend that you take a look at Tony Toews' website:
How do I get a Macro to run when the database opens... I am using the
builtin Switchboard. I need to verify the invoice has been fully paid BEFORE
allowing someone to continue using the application. I have everything else
done... presently, they can NOT update anything... but... they can list and
report on existing information. They could then export content and import it
into their own 'vehicle'.
I thought DISALLOWING everything might be more persuausive.
Will I be 'able to break in' using the shift-bypass in my Dev system?
Sorry to ask if this has been asked and answered already!
Also, the value I use to test 'lock out', gets altered during a process
invoked from the Switchboard menu... is there a way to re-invoke the macro
to test this? Wondering... not a big deal; I have some other traps to check
for this condition... just wondering.
What I mean to say is that if the value changes during events while running
the program the load on opening of the Switchboard wouldn't be invoked...
it's not recursive and doesn't know that the value has changed... just
wondered if there was an event for switching from a submenu back to main
menu. I would tie the run macro to that... I do have some backup tests that
will kill the program otherwise...
Pretty dang good if I say so myself!
Had a lot of help from the friendly folks here...
Thanks again all!
Gary D
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
