Problem with Code

PicassoB

Novice
Local time
Today, 12:43
Joined
May 7, 2007
Messages
63
Please help - Could anyone spot what has gone wrong with this calendar that I down loaded from the forum - I have tried to use it with one of my systems, but found the top two rows will not delete the added data, the bottom two are fine

I have checked the the code but canot see anthing different from the top two rows
 

Attachments

I opened it in ac2007 and it seems to perform as one would expect.
 
Same here, using A2003. It works as advertised.

Bob
 
picassso

since you are in UK, and RG, and Bob are in US, and your problem is affecting lower dates, i think almost certainly its a us/uk date thing

if you use sql, then dates such as 12/03 are taken as dec 3rd, not march 12th, unless you force them to be treated as uk dates - whereas a date that cant be ambiguous 19/03 is only treated as 19th march

i would have a look at that first
 
Good catch Gemma! The system will not let me give you any more points just yet. :(
 
you get used to date issues in uk, that i'm sure just never worry US coders
 
Gemma -

Great catch! I'd have never figured that out. You European folks have just got it all figured out -- now, if we could just get you to do dates in a sane/safe manner.

RG -

A happy Monday from the heart of the Ozarks.

Best wishes all - Bob

---

P.S. -- Have you ever given thought to the monsters we see here on this (and other) forums regarding date format? Here's my date, Mar1609, you figure it out. What's the aversion to date/time data format?

What's wrong with:

Code:
x = now()
? x
3/16/2009 4:52:10 AM 
? cdbl(x)
 39888.2028935185

Oh well?!
 
Last edited:
On the subject of date formats surely MM/DD/YYYY is less logical than DD/MM/YYYY or YYYY/MM/DD. IMHO the most sensible format is YYYY/MM/DD as it sorts properly both as a date and as a string.

However they aren't going to change so we will just have to live with them (sigh)
 
i think the distinction between MM/DD and DD/MM is just what you are used to. In UK we automatically write and think NUMERIC dates as DD/MM,

ie 27/08 always, pretty much, and never 08/27

but i think we "say" dates either way longhand - perhaps even predominantly Month first

27th August OR August 27th (my birthday, as it happens)

-----------------
i certainly agree that yyyy/mm/dd is always logical for text based dates, and you see this in older legacy systems
 
Thanks Guys
enjoyed the dialog - but has any one looked at the code to spot the problem or can tell me what I require to change, would appreciate help, as the calendar is just what I need to add to my bodyshop system
 
Thank RG works great must look at the code and see the changes
realy appreciate the exerlent responce
 
I only changed two places in the frmInputBox. In the OK Button code and the Delete Button code. Glad it worked for you.
 

Users who are viewing this thread

Back
Top Bottom