By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,105 Members | 2,560 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,105 IT Pros & Developers. It's quick & easy.

Problem with date formats in international project.

P: n/a
I try to use MS Access application as data entry/verification tool in a
multi-centre international project, where each centre uses this
application for local project management and data collection. Regularly
the data are being unloaded , confidential information is masked, and
modified data are being sent to me for pooling and analysis.
One serious problem has emmerged recently: there are some centres where
local format for dates is yyyy-mm-dd, which is in coflict with input
mask specified for fields dd/mm/yyyy.
Does somebody have a feasible solution for this problem. I was looking
for possiblity to change local(national) settings automatically while
starting the application. However this seems to be not possible with VB.
Any other suggestions?
--
Vlad
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Vladislav Moltchanov wrote:
I try to use MS Access application as data entry/verification tool in a
multi-centre international project, where each centre uses this
application for local project management and data collection. Regularly
the data are being unloaded , confidential information is masked, and
modified data are being sent to me for pooling and analysis.
One serious problem has emmerged recently: there are some centres
where local format for dates is yyyy-mm-dd, which is in coflict with
input mask specified for fields dd/mm/yyyy.
Does somebody have a feasible solution for this problem. I was
looking for possiblity to change local(national) settings automatically
while starting the application. However this seems to be not possible
with VB. Any other suggestions?

I created a text box; Text0. Here's what I had in my AfterUpdate event
Private Sub Text0_AfterUpdate()
incIt = incIt + 1
If incIt Mod 2 = 0 Then
Me.Text0.InputMask = "99/99/0000;0;_"
Me.Text0.Format = "mm/dd/yyyy"
Else
Me.Text0.InputMask = "0000/99/99;0;_"
Me.Text0.Format = "yyyy/mm/dd"
End If
MsgBox Me.Text0.InputMask & vbNewLine & Me.Text0.Format

End Sub

Maybe you can set the input mask/format in the field when the form opens.
Nov 13 '05 #2

P: n/a
Vladislav Moltchanov wrote:
I try to use MS Access application as data entry/verification tool in a
multi-centre international project, where each centre uses this
application for local project management and data collection. Regularly
the data are being unloaded , confidential information is masked, and
modified data are being sent to me for pooling and analysis.
One serious problem has emmerged recently: there are some centres
where local format for dates is yyyy-mm-dd, which is in coflict with
input mask specified for fields dd/mm/yyyy.
Does somebody have a feasible solution for this problem. I was
looking for possiblity to change local(national) settings automatically
while starting the application. However this seems to be not possible
with VB. Any other suggestions?


The thing to do especially in international applications is to use the
international date format yyyy-mm-dd as it's unambiguous, the input mask
dd/mm/yyyy will some accept dates entered in mm/dd/yyyy format so the
1st of April could be interpreted as the 4th of Jan. This is probably
another problem for you already whether you realise it or not.

I once thought that using medium or long dates was the answer to
international problems but was caught out when a user exported data to
another system with all the date names spelt in Turkish, the other
system didn't have a clue and rejected the whole lot (several megabytes
FTP'd over a painfully slow connection). The international format is
unambiguous and readable in all languages that I'm aware of.

--
[OO=00=OO]
Nov 13 '05 #3

P: n/a
I have used yyyy-mm-dd only for several years. Access, JET including
its SQL, MS-SQL, ADO, and ASP have always interpreted these correctly.
In my opinion, there is nothing for you to do.

Nov 13 '05 #4

P: n/a
I *always* use Clng(Datevalue) in the 'national' app
(I live in Holland and we have dateformat dd-mm-yyyy)
to make sure the dates are interpreted correctly.
If you can make sure they send the data to you in this format there is NO problem or conflict.

Arno R

"Vladislav Moltchanov" <vl******************@ktl.fi> schreef in bericht news:d8**********@oxygen.ktl.fi...
I try to use MS Access application as data entry/verification tool in a
multi-centre international project, where each centre uses this
application for local project management and data collection. Regularly
the data are being unloaded , confidential information is masked, and
modified data are being sent to me for pooling and analysis.
One serious problem has emmerged recently: there are some centres where
local format for dates is yyyy-mm-dd, which is in coflict with input
mask specified for fields dd/mm/yyyy.
Does somebody have a feasible solution for this problem. I was looking
for possiblity to change local(national) settings automatically while
starting the application. However this seems to be not possible with VB.
Any other suggestions?


--
Vlad

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.