[AccessD] Date standardization

Jim Lawrence accessd at shaw.ca
Wed Jun 16 15:39:35 CDT 2010


Hi Gustav:

I have been given a slight reprieve as the client is asking that I wait
until the accounts have been fully entered before I will be sent a copy of
the data. So then we shall find out what the problem is.

Jim

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, June 16, 2010 12:35 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Date standardization

Hi Jim

This can only happen if dates are not stored as data type date/time but as
text, and this can cause all sorts of trouble as validation is not possible
at the table level.
If "wrong" dates are stored, say 12/5/2010 as 5/12/2010, only manual
correction is possible unless you in some other way can sort the records.

/gustav


>>> accessd at shaw.ca 16-06-2010 07:24 >>>
Hi Steve:

Thanks for that but my dates problems appear to be related to various date
formats that a number of the data tables have in them. I only have access to
the FE and my test BE but the real BE is where the problem is. For some
reason there are date issues related to the data in the 'other' BE. If I
could get to the problem data it could be solved in minutes but currently, I
just do not know why there is a date problem and no amount of coding seems
to be able to resolve it.

Confused? So am I.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Schapel
Sent: Tuesday, June 15, 2010 7:47 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Date standardization

Hi Jim,

Are you talking about the way the dates are entered?  If these data is going

into a Date/Time data type field, then I think it doesn't make any 
difference at all how the dates are entered, as long as it is a format 
recognised as vaid by your regional settings.  The Format of the control 
where the dates are entered/displayed will determine how they are shown 
after they have been entered, but unless you do cruel things like input 
masks, the actual entry can be variable.  Therefore you can have a textbox 
with its Format property set to dd mmm yyyy and then in that textbox you can

enter 12/5 (current year will be assumed) and then you will see 12 May 2010.

Or have I misunderstood your question?

Regards
Steve


--------------------------------------------------
From: "Jim Lawrence" <accessd at shaw.ca>
Sent: Wednesday, June 16, 2010 5:57 AM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: [AccessD] Date standardization

> Hi All:
>
> I have been working on a remote site and I have been having problems with
> dates. In this application, I did not have control for its conception and
> date issues keep popping up from time to time.
>
> In all the spots I can find, I have forced the entry of a date standard
'dd
> Mon yyyy'...i.e. 12 May 2010. There are probably 50 date entry points in
> this application and another bunch of date display and report dates that
> have to be handled.
>
> As I do not have complete control over the system, is there a way under
> program control to set the default date entry to dd Mon yyyy? For both FE
> and BE?
>
> MTIA
> Jim



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list