Doug Steele
dbdoug at gmail.com
Thu Apr 10 22:15:34 CDT 2008
Yes, whenever you pass a date into SQL, I think the safest way is to pass it as cdate(Format(mydate,"mm/dd/yy")). I've had different users on a network set the default date to both yy/mm/dd and dd/mm/yy. Doug Steele On Thu, Apr 10, 2008 at 7:13 PM, Darryl Collins <Darryl.Collins at coles.com.au> wrote: > > > > >From memory all dates in VBA are treated as US dates regardless of your > regional settings and you have to code around this. > > cheers > Darryl. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Lembit Soobik > Sent: Friday, 11 April 2008 4:07 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] An International Consideration > > > LOL, > but look out for trouble with dates in VBA. I remember there was a bad > behaviour also wrt dates in German and US. cannot remember the details, > sorry, too long ago. > > Lembit > > ----- Original Message ----- > From: "Andy Lacey" <andy at minstersystems.co.uk> > To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> > Sent: Thursday, April 10, 2008 3:54 PM > Subject: Re: [AccessD] An International Consideration > > > > That was my idiocy Lembit. Do Until .Dernier is not part of VB at all. I > > was > > looking at code in a Class where Dernier was just a property the author > > created. Doh! > > > > -- > > Andy Lacey > > http://www.minstersystems.co.uk > > > > > > > > --------- Original Message -------- > > From: "Access Developers discussion and problem solving" > > <accessd at databaseadvisors.com> > > To: "Access Developers discussion and problem solving" > > <accessd at databaseadvisors.com> > > Subject: Re: [AccessD] An International Consideration > > Date: 10/04/08 13:46 > > > > > > Andy, > > it's the same with German/English Access. I remember stumbling into this > > when I first time used my German version for a US project about 10 years > > ago. was very mad on this. > > But the Do until .Dernier is new to me, and I think pretty crazy. > > > > Lembit > > > > ----- Original Message ----- > > From: "Andy Lacey" <andy at minstersystems.co.uk> > > To: "Access Developers discussion and problem solving" > > <accessd at databaseadvisors.com> > > Sent: Thursday, April 10, 2008 12:23 PM > > Subject: Re: [AccessD] An International Consideration > > > > > >> To add to this unilateral discussion. > >> > >> My French colleague tells me he could have used [Forms] rather than > >> [Formulaires] - the French version will accept French or English > whereas > >> the > >> English version only "speaks" English (how typical is that!). So the > >> moral > >> is that if you're coding in another language and want your software to > be > >> usable elsewhere use the English keywords (ok that's not so > surprising). > >> > >> But what I do find surprising is that my assumption that VB was all > >> English > >> is wrong. The statement > >> > >> Do Until .EOF > >> can be written in Franglais in the French version as > >> Do Until .Dernier > >> > >> and, what's more, my English Access understands it!! Sacre bleu. > >> > >> -- > >> Andy Lacey > >> http://www.minstersystems.co.uk > >> > >> > >> > >> --------- Original Message -------- > >> From: "Access Developers discussion and problem solving" > >> <accessd at databaseadvisors.com> > >> To: "Access Developers discussion and problem solving" > >> <accessd at databaseadvisors.com> > >> Subject: [AccessD] An International Consideration > >> Date: 10/04/08 08:34 > >> > >> > >> Hi everyone > >> > >> Here's a funny thing that's arisen because of running an Access system > >> written in French on an English version of Access. I thought those of > you > >> involved in systems around the globe might be interested in this. > >> > >> I found that when I open a form whose data is based upon a selection > made > >> on > >> the previous form Access pops up the parameter entry dialog and asks me > >> to > >> enter the value which it ought to be just reading from the earlier > form. > >> So > >> say I'm in form A. There's a prompt for a week number and then a button > >> to > >> open the production plan for that week. In France, where the system was > >> written, that week's plan would appear. Here in the UK Access pops up a > >> dialog asking for the week number and only when I enter it there does > the > >> plan appear. This behaviour occurs all over the systems. What it is, > I'm > >> sure, is that the recordsource for the planning screen is: > >> > >> SELECT * > >> FROM [Pr?paration planning] > >> WHERE [Pr?paration planning].Semaine=[Formulaires]![Semaine > >> planning]![Semaine] > >> > >> If you look at the WHERE statement the keyword Formulaires is not being > >> recognised in English Access (it would be Forms here of course) so > >> [Formulaires]![Semaine planning]![Semaine] is being treated as an > unknown > >> parameter and Access asks for user input. > >> > >> Interesting eh? Of course what I could do is get hold of a French > version > >> of > >> Access but I'd need to install that on another machine as it would be > >> sure > >> to get in the way of the English version. A case for Virtual PC, I > know. > >> Anyway this post is not about solving this (unless someone has a great > >> idea > >> of course), more about pointing out yet another potential pratfall when > >> you > >> cross national/language borders. I'd be interested to know if Access > >> handles > >> the reverse ok, ie if [Forms] is used would that be ok in the French > >> version? > >> > >> -- > >> Andy Lacey > >> http://www.minstersystems.co.uk > >> > >> > >> ________________________________________________ > >> Message sent using UebiMiau 2.7.2 > >> > >> -- AccessD mailing list > >> AccessD at databaseadvisors.com > >> http://databaseadvisors.com/mailman/listinfo/accessd > >> Website: http://www.databaseadvisors.com > >> > >> ________________________________________________ > >> Message sent using UebiMiau 2.7.2 > >> > >> -- > >> AccessD mailing list > >> AccessD at databaseadvisors.com > >> http://databaseadvisors.com/mailman/listinfo/accessd > >> Website: http://www.databaseadvisors.com > >> > >> > >> -- > >> No virus found in this incoming message. > >> Checked by AVG. > >> Version: 7.5.519 / Virus Database: 269.22.11/1368 - Release Date: > >> 09.04.2008 16:20 > >> > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > ________________________________________________ > > Message sent using UebiMiau 2.7.2 > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG. > > Version: 7.5.519 / Virus Database: 269.22.11/1368 - Release Date: > > 09.04.2008 16:20 > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > This email and any attachments may contain privileged and confidential > information and are intended for the named addressee only. If you have > received this e-mail in error, please notify the sender and delete this > e-mail immediately. Any confidentiality, privilege or copyright is not > waived or lost because this e-mail has been sent to you in error. It is your > responsibility to check this e-mail and any attachments for viruses. No > warranty is made that this material is free from computer virus or any other > defect or error. Any loss/damage incurred by using this material is not the > sender's responsibility. The sender's entire liability will be limited to > resupplying the material. > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >