Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Prevent users to print in a preview mode
Message
From
06/07/1999 18:09:09
 
 
To
06/07/1999 14:54:10
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00229460
Message ID:
00237988
Views:
10
>>This is a way around that will keep most user to suspect anything if the files are names wisely. Good idea. Thank you.
>>
>>But still, the reason I asked that is because I use this application as a demo. This demo is available to my possible clients that want to evaluate our software. This is why I don't want them to print because they will be able to use it whitout buying it. Sure I have other protection that will protect my application but this is the only one that tickles me.
>
>My way of demoing is to have all the options active, including printing - only to limit the number of records in the tables. Another thing is that all the reports include user's company name in the top left, and in the case of a demo version, the company name is "Demo version". So they may print it as much as they like.

Hi Dragan

Of course your idea is the ideal one but in case a functionality like the one described by Robert has to be:

I was wondering what could happen if you include a copy of the foxuser file into the project with another name like ‘BackUpUser’ and overwrite the original foxuser every time the application is started.

Use BackUpUser
Copy to foxuser with cdx

It could be more sophisticated if you start VFP with no foxuser file in order to have VFP to create a new one and then remove any toolbar buttons or do any configuration which gets stored into foxuser, quit VFP so foxuser gets updated an then open it as the first thing next time you open VFP in order to save it with this new changes. Then the application could ‘lookup’ for changes and replace them with the original ones and in case they have been removed, insert them again.

Probably too complicated but might work.

A couple if things could be considered here:
Is there a CRC checking or any other kind of corruption being checked by VFP into the foxuser file? If so it could crash or just do nothing.

You may have to reload configurations from FoxUser (which I have no idea of how to do it) or probably quit the application so the user starts again with the FoxUser file updated.

Oscar Corte
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform