Robin- Actually, I think picking a name that "looks" like a real property but isn't is even more devious. Because George wants to test date/time, he could create a Double data type property and convert the value to a pure number. Even if the user does discover the custom property, it won't be obvious how it's being used or how to reset it so the program isn't "expired" anymore.
John Viescas, author "Building Microsoft Access Applications" "Microsoft Office Access 2003 Inside Out" "Running Microsoft Access 2000" "SQL Queries for Mere Mortals" http://www.viescas.com/ > -----Original Message----- > From: ms_access@yahoogroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of Robin > Sent: Tuesday, May 10, 2005 6:50 AM > To: ms_access@yahoogroups.com > Subject: [ms_access] Re: Set System Date > > > Hello George, > > You have to remember, there is always a way, if you can set it so > can someone else. The trick lies in wether they can figure out where > you put the info. > > I tend to make property names as wierd as possible. Others will > disagree but it works for me. > > Regards > Robin. > > > --- In ms_access@yahoogroups.com, "George Oro" <[EMAIL PROTECTED]> wrote: > > Thanks Robin... I managed how to do it as per John V. instruction. > > > > Now I hard coded all my Secret Values using custom properties in > one > > Module inside my FrontEnd.mde > > Last doubt: > > is there any *way* for the user to VIEW & CHANGE my values? I hope > > nothing... > > > > TIA, > > George > > > > > > -----Original Message----- > > From: ms_access@yahoogroups.com [mailto:[EMAIL PROTECTED] > On > > Behalf Of Robin > > Sent: Monday, May 09, 2005 5:27 PM > > To: ms_access@yahoogroups.com > > Subject: [ms_access] Re: Set System Date > > > > > > Hello George, > > > > Certainly you can. If you create a property as text, I see no > reason > > why you can't generate a delimited string of whatever values you > > want to make. > > > > Regards > > Robin. > > > > > > --- In ms_access@yahoogroups.com, "George Oro" <[EMAIL PROTECTED]> wrote: > > > Hi Robin, > > > > > > What do you mean, every log you can save the date/time without > > using a > > > table? If so, this is great otherwise, sorry... > > > > > > TIA, > > > George > > > > > > > > > > > > -----Original Message----- > > > From: ms_access@yahoogroups.com > [mailto:[EMAIL PROTECTED] > > On > > > Behalf Of Robin > > > Sent: Monday, May 09, 2005 5:12 PM > > > To: ms_access@yahoogroups.com > > > Subject: [ms_access] Re: Set System Date > > > > > > > > > Hello John, > > > > > > Wouldn't it be less work to store the date in a user defined > > > property, if that's the only thing that's causing a problem? > > > > > > Regards > > > Robin. > > > > > > > > > --- In ms_access@yahoogroups.com, "John Viescas" <[EMAIL PROTECTED]> > > wrote: > > > > George- > > > > > > > > No extra mdb or mde required, but you will need to distribute > > your > > > mdw as > > > > part of the install and point to it with a shortcut that starts > > > your > > > > application. You will "secure" your mde, but the only object > > > actually > > > > secured will be your "hidden" table. You'll open that in code > > > by "signing > > > > on" in a new workspace using the userid and password known only > > to > > > you - the > > > > one userid that's authorized to read/write the hidden table. > > > > > > > > Dim ws As DAO.Workspace, db As DAO.Database, rst As > DAO.Recordset > > > > > > > > Set ws = CreateWorkspace("SecureWS", _ > > > > "<userid>", "<password>", dbUseJet) > > > > Set db = ws.OpenDatabase(CurrentProject.FullName, False, > False) > > > > Set rst = db.OpenRecordset("ztblSystem", dbOpenDynaset) > > > > > > > > Now rst points to your system table named ztblSystem, and you > can > > > read/write > > > > it in code at will as long as you supplied the correct user and > > > password in > > > > the CreateWorkspace. > > > > > > > > John Viescas, author > > > > "Building Microsoft Access Applications" > > > > "Microsoft Office Access 2003 Inside Out" > > > > "Running Microsoft Access 2000" > > > > "SQL Queries for Mere Mortals" > > > > http://www.viescas.com/ > > > > > > > > > -----Original Message----- > > > > > From: ms_access@yahoogroups.com > > > > > [mailto:[EMAIL PROTECTED] On Behalf Of George Oro > > > > > Sent: Monday, May 09, 2005 2:35 AM > > > > > To: ms_access@yahoogroups.com > > > > > Subject: RE: [ms_access] Set System Date > > > > > > > > > > > > > > > Very interesting John. I normally used workgroup but not on > > > > > this project I'm > > > > > working on because I don't want my vendor to bother with > > > > > this. Basically my > > > > > setting is: > > > > > 1) FE is mde and AllowBypassKey=False > > > > > 2) BE with one startup form, database password and > > > > > AllowBypassKey=False > > > > > 3) Used access default system.mdw. > > > > > Do you have any additional security? > > > > > > > > > > > > > > > >From your idea, I have to create a separate .mdb that is > > > > > fully secured using > > > > > a custom workgroup. If so, here's my doubt: > > > > > 1) It will be look suspicious this new .mdb file, hide maybe > > > > > somewhere? > > > > > 2) Could you guide me to connect to a secured mdb using code > > > > > (workspace) > > > > > never tried yet. > > > > > 3) In case a user found the exact structure and data of the > > > > > secured mdb, > > > > > what will happen if the user will create a replica of that > > > > > mdb and overwrite > > > > > it? > > > > > > > > > > TIA, > > > > > George > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: ms_access@yahoogroups.com > > > [mailto:[EMAIL PROTECTED] > > > > > Behalf Of John Viescas > > > > > Sent: Sunday, May 08, 2005 6:00 PM > > > > > To: ms_access@yahoogroups.com > > > > > Subject: RE: [ms_access] Set System Date > > > > > > > > > > > > > > > George- > > > > > > > > > > Well, yes, an "advanced" user might figure it out. You have > > > > > to weigh the > > > > > likelihood that a few advanced users might get around your > > > > > trap versus the > > > > > trouble to fully secure it. You could create a custom > > > > > workgroup, define one > > > > > user with a password that has permission to touch the hidden > > > > > table, and then > > > > > in code open a Workspace with that userid to read/write the > > > > > table. You > > > > > wouldn't bother to secure anything else. If the user tries > > > > > to run without > > > > > your workgroup file, the app won't run at all (your create > > > > > workspace will > > > > > fail, and you'll bail on the error trap). If the user tries > > > > > to find and > > > > > open your "log" table, Access will lock them out with a > > > > > security violation. > > > > > But is it worth this much trouble? > > > > > > > > > > John Viescas, author > > > > > "Building Microsoft Access Applications" > > > > > "Microsoft Office Access 2003 Inside Out" > > > > > "Running Microsoft Access 2000" > > > > > "SQL Queries for Mere Mortals" > > > > > http://www.viescas.com/ > > > > > > > > > > > -----Original Message----- > > > > > > From: ms_access@yahoogroups.com > > > > > > [mailto:[EMAIL PROTECTED] On Behalf Of George Oro > > > > > > Sent: Sunday, May 08, 2005 8:39 AM > > > > > > To: ms_access@yahoogroups.com > > > > > > Subject: RE: [ms_access] Set System Date > > > > > > > > > > > > > > > > > > Thanks a lot John, I know there's a lot of way to control > > > > > > this trial version > > > > > > but my problem and doubt is, how can I secure the table > where > > > > > > the logs are > > > > > > getting entered? Correct me if I'm wrong, even your app is > an > > > > > > mde and your > > > > > > log table is hidden, advanced users can still alter the > data > > > > > > you have on the > > > > > > table is in it? > > > > > > > > > > > > I wish you have a way to secure a table to avoid from > > > > > > altering the data. > > > > > > > > > > > > TIA, > > > > > > George > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: ms_access@yahoogroups.com > > > [mailto:[EMAIL PROTECTED] > > > > > > Behalf Of John Viescas > > > > > > Sent: Sunday, May 08, 2005 5:00 PM > > > > > > To: ms_access@yahoogroups.com > > > > > > Subject: RE: [ms_access] Set System Date > > > > > > > > > > > > > > > > > > George- > > > > > > > > > > > > In one application I created that allowed for a "30 day > > > > > free trial," I > > > > > > logged each session start to a hidden table and compared > the > > > > > > date/time of > > > > > > the last run with the system clock. If the user had set > the > > > > > > clock backwards > > > > > > (current time earlier than the last time they ran the > > > > > application), I > > > > > > displayed an error message, set a flag to disallow using > the > > > > > > program any > > > > > > further, and exited. The user was forced to reinstall and > > > > > > fix the clock to > > > > > > get it working again. > > > > > > > > > > > > I believe there's an API call you could use to reset the > > > > > > clock - perhaps > > > > > > using the NET command to fetch the time off a server. If > the > > > > > > machine has an > > > > > > internet connection, you can set options in Windows XP to > > > > > > sync with one of > > > > > > the atomic clocks over the internet. > > > > > > > > > > > > John Viescas, author > > > > > > "Building Microsoft Access Applications" > > > > > > "Microsoft Office Access 2003 Inside Out" > > > > > > "Running Microsoft Access 2000" > > > > > > "SQL Queries for Mere Mortals" > > > > > > http://www.viescas.com/ > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: ms_access@yahoogroups.com > > > > > > > [mailto:[EMAIL PROTECTED] On Behalf Of George > Oro > > > > > > > Sent: Sunday, May 08, 2005 4:01 AM > > > > > > > To: YG Access > > > > > > > Subject: [ms_access] Set System Date > > > > > > > > > > > > > > > > > > > > > Let say the user changed the system date 1 day backward, > > how > > > > > > > my program can > > > > > > > set this back on the current date? Let say one form will > > open > > > > > > > and do it. > > > > > > > > > > > > > > Forgive me if I'm asking a stupid question... because on > > top > > > > > > > of my head the > > > > > > > program doesn't have any other source where to get the > > > > > current date. > > > > > > > Perhaps Atomic?) > > > > > > > > > > > > > > > > > > > > > TIA, > > > > > > > George > > > > > > > > > > > > > > > > > > > > > > > > > > > > [Non-text portions of this message have been removed] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > Yahoo! Groups Links > > > > > > Yahoo! Groups Links > > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/ms_access/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
