Hale, Jim
Jim.Hale at FleetPride.com
Wed Mar 21 14:00:46 CDT 2007
ROTFL! It had to be alpha numeric because a DB that old probably used roman numerals for dates. Come to think of it it probably followed the Julian calendar as well. Jim Hale -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of JWColby Sent: Wednesday, March 21, 2007 10:56 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] OT(kinda): Crack Code >..all of the Keys are 8 character alpha-numeric LOL, good reason to no longer exist! John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte Sent: Wednesday, March 21, 2007 11:49 AM To: accessd at databaseadvisors.com Subject: [AccessD] OT(kinda): Crack Code Hello All, I have a DB...just the data...no FE...all of the Keys are 8 character alpha-numeric. This key is generated from the date time. The company that developed the app no longer exists. I need to figure out the logic used, and convert these keys back to date time. I've searched online for any reference to the company/software...and no luck. Any ideas/directions...anything? Thanks, Mark A. Matte _________________________________________________________________ Its tax season, make sure to follow these few simple tips http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTips.a spx?icid=HMMartagline -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com *********************************************************************** The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. As a recipient of this email, you are responsible for screening its contents and the contents of any attachments for the presence of viruses. No liability is accepted for any damages caused by any virus transmitted by this email.