Avoid user change Windows DATE 4

[eys]

I have a lot of problems with my Vfox aplicattions that use DATE() (system time) to work well, when the user click's the DATE display in the startup bar.

The user can change the date and make problems with my aplicattion.

IS THERE A WAY TO AVOID THE USER CHANGE SYSTEM TIME? I mean under Win98 / ME.

Thanks

Jose Carlos

 

[ramani]

Hi
1. If the workstations are connected to a server, you can have the computers time set as that of the server, every time they start your fox application.

2. If the users are just ignorant (and so misusing the clock), then you can disable the clock in the task bar.
Right Click on the CLOCK/TIME on the tray.. Select Properties.. Remove the check for SHOW CLOCK. Apply it.
But any one can get in.. easily..

3. Even if you disable the clock... users can go to DOS prompt and change it by TIME command or DATE command.

Hope this helps you ramani :-9
(Subramanian.G),FoxAcc, ramani_g@yahoo.com

 

[DSummZZZ]

Also, you can disallow users from getting to the date and time settings once they are set by renaming or deleting TIMEDATE.CPL located in the system directory.

Dave S.

 

[DSummZZZ]

As an addendum to my prior post, you can still manually set the date and time by going to Start->Run and inputting the following command, which assumes you have renamed TIMEDATE.CPL to TIMEDATE.HID:

CONTROL TIMEDATE.HID

Dave S.

 

[eys]

VOILA!!! I was afraid that this question does not belong to this kind of forum, but this are generous and love this "job".

Thanks a Lot. Muchas Gracias amigos.

Jose Carlos

 

[rajrajcoomar]

Try this:

If your application is DATE() sensitive, have the user confirm the DATE() each time your application starts. Since your application should have some level of security, you can log the user that provided the DATE() in case yuo need to audit. You can even test the input with the system date using a validation routine

There's a global VFP variable named _DIARYDATE. The default value is the system date. Update _DIARYDATE with the user's input and use _DIARYDATE instead of DATE() throughout your application. _DIARYDATE will not be updated by any changes made to the system date until the next session of your application. And then you go through the validation process again!

 

[jonscott8]

PMFJI, but if any vender/application informed myself that I would not be allowed to modify MY COMPUTER's date/time - they could rest assured my dollars would be headed elsewhere.

And even if the PC is on your corporate owned network, I still feel it's bad practice to attempt to prevent the user from modifying their PC settings.

You'd be better off modifying your application to retrieve the DATETIME() from a centralized server. There are examples here to illustrate how to do this. Jon Hawkins

 

[DSummZZZ]

My two cents.
Even with the dark cloud of termination looming over their heads, some employees still insist on messing around with systems and settings that they shouldn't be touching. A lot of times, one person is to blame for inconveniencing everyone else. And you are right, there are other ways to go about it, but until another solution is implemented, brute force may be required.

Dave S.