I?m sure that many of you earn your living by developing Access databases. 
Have you ever had the client who thinks that your there to write for 
him/her a free database. In other words being paid by them is like asking 
a squadron of pigs to take to the sky.

So, I?m searching for a idea on how to automatically disable a database 
after a period of time if the money has not supplied in the right quantity 
and in the right time scale. 

I?m sure I?m not the first to experience this little problem. 

Any ideas on time base database disabling folks?

johnb  

One thing I do is give them an mde. I have a module that is read by the start up program that checks the date. If the date is
greater than the date I desire a msg box pops up tells them that the database has expired and to contact me. It then shuts down the
database. Since it is an mde, then cannot get to my code to change this. When I have full payment, I send them an mdb with this code
removed.
Just a thought.
 
 joh bell <johnwardbell@a...> wrote:
I?m sure that many of you earn your living by developing Access databases. 
Have you ever had the client who thinks that your there to write for 
him/her a free database. In other words being paid by them is like asking 
a squadron of pigs to take to the sky.

So, I?m searching for a idea on how to automatically disable a database 
after a period of time if the money has not supplied in the right quantity 
and in the right time scale. 

I?m sure I?m not the first to experience this little problem. 

Any ideas on time base database disabling folks?

johnb 


Lonnie Johnson
ProDev, Professional Development of MS Access Databases
http://www.prodev.us
Let me build your next MS Access database application. 




 



---------------------------------
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day

Very smart

>>> prodevmg@y... 02/14/03 11:27AM >>>

One thing I do is give them an mde. I have a module that is read by the
start up program that checks the date. If the date is greater than the
date I desire a msg box pops up tells them that the database has expired
and to contact me. It then shuts down the database. Since it is an mde,
then cannot get to my code to change this. When I have full payment, I
send them an mdb with this code removed.
Just a thought.
 
 joh bell <johnwardbell@a...> wrote:
IĈm sure that many of you earn your living by developing Access
databases. 
Have you ever had the client who thinks that your there to write for 
him/her a free database. In other words being paid by them is like
asking 
a squadron of pigs to take to the sky.

So, IĈm searching for a idea on how to automatically disable a database

after a period of time if the money has not supplied in the right
quantity 
and in the right time scale. 

IĈm sure IĈm not the first to experience this little problem. 

Any ideas on time base database disabling folks?

johnb 


Lonnie Johnson
ProDev, Professional Development of MS Access Databases
http://www.prodev.us 
Let me build your next MS Access database application. 




 



---------------------------------
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day

Heh, yeah.  Some people unfortunately think programming involves snapping 
your fingers.  It drives me nuts too.

And what's an mde?  I do Access database development and would be 
interested in learning more.

Me, too. It's called customer education. I think that, unless the customer
sees all of the hours you put in, he just has no comprehension of the effort
involved. Some customers are just sloiw learners.

Mark
----- Original Message -----
From: "Matt B." <admin@m...>
To: "Access" <access@p...>
Sent: Friday, February 14, 2003 10:58 PM
Subject: [access] Re: Getting Paid !!


> Heh, yeah.  Some people unfortunately think programming involves snapping
> your fingers.  It drives me nuts too.

I also always use mde files with a module or startup form which is date 
sensitive. Only problem is the clever so and so who tries winding back the 
computer clock. 

Am working on a way round this in the following terms. Select some field 
in the database which gets updated everytime it is used. Then in module or 
startup form compare highest date in this field with computer system 
clock. If it is higher than the system clock, put up a MsgBox with warning 
that continuing will corrupt/destroy all data. Should stop that practice?

Another means of restricting use might be to use a hidden field on
your start-up form which increments an integer with each start-up
(using the autoexec macro).  Users could be informed that Xn number of
uses are permitted under the trial period before the software must be
paid for.  On reaching the limit your message box could be fired up -
you could even , with a bit of Windows programming (I imagine - never
tried it) force the application to become read-only.

This would free you from the time tricksters - and to some extent from
those who copy your application to another machine.

Regards,
Nick

Nick,

<< Another means of restricting use might be to use a hidden field on
your start-up form which increments an integer with each start-up
(using the autoexec macro).  Users could be informed that Xn number of
uses are permitted under the trial period before the software must be
paid for. >>

I like this approach better than the date-dependent one because of system 
clock ticksters.  I would add one more thing to your code.  The desperate 
user will call up the program on Monday and not shut it down until Friday 
(if ever).  In that case, one use lasts one week and 100 uses, say, lasts 
100 weeks.  If you want to thwart that trickery as well, code something 
that says if the program is idle for X hours, then shut down the database.

[Insert Dr. Evil sinister laugh here.]

Greg

Re hidden field on the startup form. But where is the "field"? Unless I am 
missing something, a "field" on a form is bound to a field in a table. 
Even if an mde is used, tables are open access and can easily be edited by 
the user. If I'm missing something here, please let me know. Thanks.


> Another means of restricting use might be to use a hidden field on
your start-up form which increments an integer with each start-up
(using the autoexec macro).  Users could be informed that Xn number of
uses are permitted under the trial period before the software must be
paid for.  On reaching the limit your message box could be fired up -
you could even , with a bit of Windows programming (I imagine - never
tried it) force the application to become read-only.

This would free you from the time tricksters - and to some extent from
those who copy your application to another machine.

Regards,
Nick

	Try to create a front end and have the back end passworded, in that way a user cannot go into
tables directly and edit it.

enzo c",)
Yahoo ID: yackydidakdak
o!O TrOpang Watak Watak
http://www.tropangwatakwatak.tk


-----Original Message-----
From: Clive Astley [mailto:clive.astley@k...]
Sent: Wednesday, February 19, 2003 9:33 PM
To: Access
Subject: [access] RE: getting paid!!!


Re hidden field on the startup form. But where is the "field"? Unless I am 
missing something, a "field" on a form is bound to a field in a table. 
Even if an mde is used, tables are open access and can easily be edited by 
the user. If I'm missing something here, please let me know. Thanks.


> Another means of restricting use might be to use a hidden field on
your start-up form which increments an integer with each start-up
(using the autoexec macro).  Users could be informed that Xn number of
uses are permitted under the trial period before the software must be
paid for.  On reaching the limit your message box could be fired up -
you could even , with a bit of Windows programming (I imagine - never
tried it) force the application to become read-only.

This would free you from the time tricksters - and to some extent from
those who copy your application to another machine.

Regards,
Nick

	ooops sorry, this can be done only if you have a VB front end

enzo c",)

-----Original Message-----
From: Enzo Zaragoza [mailto:enzaux@g...]
Sent: Thursday, February 20, 2003 8:27 AM
To: Access
Subject: [access] RE: getting paid!!!



	Try to create a front end and have the back end passworded, in that way a user cannot go into
tables directly and edit it.

enzo c",)
Yahoo ID: yackydidakdak
o!O TrOpang Watak Watak
http://www.tropangwatakwatak.tk


-----Original Message-----
From: Clive Astley [mailto:clive.astley@k...]
Sent: Wednesday, February 19, 2003 9:33 PM
To: Access
Subject: [access] RE: getting paid!!!


Re hidden field on the startup form. But where is the "field"? Unless I am 
missing something, a "field" on a form is bound to a field in a table. 
Even if an mde is used, tables are open access and can easily be edited by 
the user. If I'm missing something here, please let me know. Thanks.


> Another means of restricting use might be to use a hidden field on
your start-up form which increments an integer with each start-up
(using the autoexec macro).  Users could be informed that Xn number of
uses are permitted under the trial period before the software must be
paid for.  On reaching the limit your message box could be fired up -
you could even , with a bit of Windows programming (I imagine - never
tried it) force the application to become read-only.

This would free you from the time tricksters - and to some extent from
those who copy your application to another machine.

Regards,
Nick

Re hidden field on the startup form. But where is the "field"? Unless I am
missing something, a "field" on a form is bound to a field in a table.
Even if an mde is used, tables are open access and can easily be edited by
the user. If I'm missing something here, please let me know. Thanks.


Tools/Options/View and select 'system objects'
Create a table with a prefix 'Usys'
Store your data in this table
Tools/Options/View and de-select 'system objects'

The table is hidden

A user who knows Access well enough can make the table visible but not if
it is an MDE.





*************************************************************************

This e-mail may contain confidential information or be privileged. It is intended to be read and used only by the named
recipient(s). If you are not the intended recipient(s) please notify us immediately so that we can make arrangements for its return:
you should not disclose the contents of this e-mail to any other person, or take any copies. Unless stated otherwise by an
authorised individual, nothing contained in this e-mail is intended to create binding legal obligations between us and opinions
expressed are those of the individual author.

The CIS marketing group, which is regulated for Investment Business by the Financial Services Authority, includes:
Co-operative Insurance Society Limited Registered in England number 3615R - for life assurance and pensions
CIS Unit Managers Limited Registered in England and Wales number 2369965  - for unit trusts and PEPs
CIS Policyholder Services Limited Registered in England and Wales number 3390839 - for ISAs and investment products bearing the CIS
name
Registered offices: Miller Street, Manchester M60 0AL   Telephone  0161-832-8686   Internet  http://www.cis.co.uk   E-mail
cis@c...

CIS Deposit and Instant Access Savings Accounts are held with The Co-operative Bank p.l.c., registered in England and Wales number
990937, P.O. Box 101, 1 Balloon Street, Manchester M60 4EP, and administered by CIS Policyholder Services Limited as agent of the
Bank.

CIS is a member of the General Insurance Standards Council

CIS & the CIS logo (R) Co-operative Insurance Society Limited

********************************************************************************

If in the Startup menu options you uncheck the "use Access special
keys" box, as well as the display database window box (which you will
have done for your startup form), and you also create a custom file
menu to prevent the recently-used files list potential workaround,
then  - in combination with creating an MDE version of your
application - you should have locked the thing down almost completely.
 The remaining workaround hack is holding down the shift key while
opening the database, which bypasses the Access startup options.  If
your users are running the application on the Access runtime
environment, this will not apply.  If they are on the retail version
then it will.  But you can prevent all of this by setting the
AllowBypassKey property, in code, to false.

How about a binding contract with your customer???

--------------- reply ----------------
> 
> Re hidden field on the startup form. But where is the "field"?
Unless I am
> missing something, a "field" on a form is bound to a field in a
table.
> Even if an mde is used, tables are open access and can easily be
edited by
> the user. If I'm missing something here, please let me know. Thanks.
> 
> 
> Tools/Options/View and select 'system objects'
> Create a table with a prefix 'Usys'
> Store your data in this table
> Tools/Options/View and de-select 'system objects'
> 
> The table is hidden
> 
> A user who knows Access well enough can make the table visible but
not if
> it is an MDE.
> 
> 
> 
> 
> 
>
**********************************************************************
***
> 
> This e-mail may contain confidential information or be privileged.
It is intended to be read and used only by the named recipient(s). If
you are not the intended recipient(s) please notify us immediately so
that we can make arrangements for its return: you should not disclose
the contents of this e-mail to any other person, or take any copies.
Unless stated otherwise by an authorised individual, nothing contained
in this e-mail is intended to create binding legal obligations between
us and opinions expressed are those of the individual author.
> 
> The CIS marketing group, which is regulated for Investment Business
by the Financial Services Authority, includes:
> Co-operative Insurance Society Limited Registered in England number
3615R - for life assurance and pensions
> CIS Unit Managers Limited Registered in England and Wales number
2369965  - for unit trusts and PEPs
> CIS Policyholder Services Limited Registered in England and Wales
number 3390839 - for ISAs and investment products bearing the CIS name
> Registered offices: Miller Street, Manchester M60 0AL   Telephone 
0161-832-8686   Internet  http://www.cis.co.uk   E-mail cis@c...
> 
> CIS Deposit and Instant Access Savings Accounts are held with The
Co-operative Bank p.l.c., registered in England and Wales number
990937, P.O. Box 101, 1 Balloon Street, Manchester M60 4EP, and
administered by CIS Policyholder Services Limited as agent of the
Bank.
> 
> CIS is a member of the General Insurance Standards Council
> 
> CIS & the CIS logo (R) Co-operative Insurance Society Limited
> 
>
**********************************************************************
**********
> 
> 
> 
N.C. Johnson, 
Centre for Manx Studies, Douglas, Isle of Man

A user who knows Access well enough can make the table visible but not if
it is an MDE.

Sorry, I don't understand this. I've just tried making an mde and it is 
still possible to unhide the system files. Or do you mean that you have to 
have a custom toolbar?

How about using a bit of handshaking.
First off generate a unique ID for that database instance (eg by using a 
timedate stamp with some random integers to encrypt it), from the unique 
ID generate another hidden ID for matching up later. The first ID (key) is 
sent to you by the customer (to unlock the app), you send them back 
another ID to complete the unlock sequence that will match the hidden ID 
stored in that database. The advantage of this is that it can only be used 
once and can only be copied if the customer makes a copy of the database 
AFTER they've requested the unlock key.

Still its better to trust your customers and make sure you get some money 
upfront. Going down the route of time limiting\disabling applications just 
pisses everyone off.


> 
I> ?m sure that many of you earn your living by developing Access 
databases. 
H> ave you ever had the client who thinks that your there to write for 
h> im/her a free database. In other words being paid by them is like 
asking 
a>  squadron of pigs to take to the sky.

> So, I?m searching for a idea on how to automatically disable a database 
a> fter a period of time if the money has not supplied in the right 
quantity 
a> nd in the right time scale. 

> I?m sure I?m not the first to experience this little problem. 

> Any ideas on time base database disabling folks?

> johnb