On-Line International time stamps (access DB)

[Wayne-I-M]

I have posted this to both the Access forum and the Frontpage forum
____________________________________

Hi

Is anyone using a website with an access DB with a time stamp - if you have,
how have you got round the time stamps being in different formats.

Driving me mad this one.

Yesterday we got a large number of payments from the UK and Peru (we have an
agency in Lima)
The access DB has a timestamp formatted Time/Date

But this of course stamps the "local" time/date
UK = 13/06/2008
Peru = 06/13/2008

I use the timestamp to validate the payment through PayPal - it's the "only"
non user input that we get on both the PayPal statements and the user input
form (to the on-line DB) so there is nothing else I can use as this is the
only data that’s the same on both streams. Everything else may or may not be
correct – ie. E mail address’ are typed and so sometime wrong on one or the
other (there is no link from the form to paypal so I can’t validate this).
The same goes for the person’s name (yes people spell their names wrong).
Etc. etc. There is only the timestamp to use.

I have tried setting the timestamp to a simple Now() - to force it to UK
format but all this does is load the local time (set from the users computer)
which is based on the regional settings of the machine being used to input
the data.

I "thought" I could code virtually anything in access but this has me
beat. I have tried using CDATE but this fails on 01/12/08 and 12/01/08 (as
they are both correct).

I have tried importing the timestamp from outlook as it's received but this
also fails 01/12/08 (and any other combination that "could" be correct)

I have tried using my local server timestamp to update AfterUpdate (but you
still get the "local" time/date

So, unless everyone in the world would like to move to London then I need to
fix this. At the momnet we are importing the DB and simply looking at the
date to see what needs to be changed - not good when there are over a
thousand payment per day

Any Ideas ?? (there "has" to be a way to do this)

 

[Stefan B Rusynko]

Client side script will always load/render the users time zone / loc settings
Server side script will always use your hosted server location time zone but render it in browser based on the users local settings

So in ASP, Now() will always be your server date/time

If you are getting the data from PayPal as say DateTime convert it before writing it to the DB

<%
MyDate= (Month(DateTime)&"/"&Day(DateTime)&"/"&Year(DateTime)
%>
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|I have posted this to both the Access forum and the Frontpage forum
| ____________________________________
|
| Hi
|
| Is anyone using a website with an access DB with a time stamp - if you have,
| how have you got round the time stamps being in different formats.
|
| Driving me mad this one.
|
| Yesterday we got a large number of payments from the UK and Peru (we have an
| agency in Lima)
| The access DB has a timestamp formatted Time/Date
|
| But this of course stamps the "local" time/date
| UK = 13/06/2008
| Peru = 06/13/2008
|
| I use the timestamp to validate the payment through PayPal - it's the "only"
| non user input that we get on both the PayPal statements and the user input
| form (to the on-line DB) so there is nothing else I can use as this is the
| only data that’s the same on both streams. Everything else may or may not be
| correct – ie. E mail address’ are typed and so sometime wrong on one or the
| other (there is no link from the form to paypal so I can’t validate this).
| The same goes for the person’s name (yes people spell their names wrong).
| Etc. etc. There is only the timestamp to use.
|
| I have tried setting the timestamp to a simple Now() - to force it to UK
| format but all this does is load the local time (set from the users computer)
| which is based on the regional settings of the machine being used to input
| the data.
|
| I "thought" I could code virtually anything in access but this has me
| beat. I have tried using CDATE but this fails on 01/12/08 and 12/01/08 (as
| they are both correct).
|
| I have tried importing the timestamp from outlook as it's received but this
| also fails 01/12/08 (and any other combination that "could" be correct)
|
| I have tried using my local server timestamp to update AfterUpdate (but you
| still get the "local" time/date
|
| So, unless everyone in the world would like to move to London then I need to
| fix this. At the momnet we are importing the DB and simply looking at the
| date to see what needs to be changed - not good when there are over a
| thousand payment per day
|
| Any Ideas ?? (there "has" to be a way to do this)
|
| --
| Wayne
| Manchester, England.
|
|

 

[Wayne-I-M]

Hi Stefan

I have tried this

If you are getting the data from PayPal as say DateTime convert it before writing it to the DB

But I can't see how to do this (I think it can't be done)
01/11/2009 could be 11/01/2008
I can use DatePart to extract the segments and "re-do" them but which part
do I "re-do". They could both be correct.

The lines I am going down at the moment (I understand it's a little mad -
but can't think of anything else) it to assume that inputs were always made
within the last week (we import daily except for weekends). If the timestamp
is
01/11/2009 and today is 13th January 2009 I can write an update on import no
problems and convert to 11/01/2009 - but thats all I can think off at the
moment. This will only fail during the chritstmas period when imports are
stopped for 10 days

Maybe I need a coffee to make it all work

So in ASP, Now() will always be your server date/time

I am only slightly just getting into server side scripts ( just got
expression web - and running though a new on-line booking system to go live
this december with that). So I will keep your answer and try and bring this
into the form design for the new setup.

Many thanks - that seems to be the way forward





--
Wayne
Manchester, England.

Client side script will always load/render the users time zone / loc settings
Server side script will always use your hosted server location time zone but render it in browser based on the users local settings

So in ASP, Now() will always be your server date/time

If you are getting the data from PayPal as say DateTime convert it before writing it to the DB

<%
MyDate= (Month(DateTime)&"/"&Day(DateTime)&"/"&Year(DateTime)
%>
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|I have posted this to both the Access forum and the Frontpage forum
| ____________________________________
|
| Hi
|
| Is anyone using a website with an access DB with a time stamp - if you have,
| how have you got round the time stamps being in different formats.
|
| Driving me mad this one.
|
| Yesterday we got a large number of payments from the UK and Peru (we have an
| agency in Lima)
| The access DB has a timestamp formatted Time/Date
|
| But this of course stamps the "local" time/date
| UK = 13/06/2008
| Peru = 06/13/2008
|
| I use the timestamp to validate the payment through PayPal - it's the "only"
| non user input that we get on both the PayPal statements and the user input
| form (to the on-line DB) so there is nothing else I can use as this is the
| only data that’s the same on both streams. Everything else may or may not be
| correct – ie. E mail address’ are typed and so sometime wrong on one or the
| other (there is no link from the form to paypal so I can’t validate this).
| The same goes for the person’s name (yes people spell their names wrong).
| Etc. etc. There is only the timestamp to use.
|
| I have tried setting the timestamp to a simple Now() - to force it to UK
| format but all this does is load the local time (set from the users computer)
| which is based on the regional settings of the machine being used to input
| the data.
|
| I "thought" I could code virtually anything in access but this has me
| beat. I have tried using CDATE but this fails on 01/12/08 and 12/01/08 (as
| they are both correct).
|
| I have tried importing the timestamp from outlook as it's received but this
| also fails 01/12/08 (and any other combination that "could" be correct)
|
| I have tried using my local server timestamp to update AfterUpdate (but you
| still get the "local" time/date
|
| So, unless everyone in the world would like to move to London then I need to
| fix this. At the momnet we are importing the DB and simply looking at the
| date to see what needs to be changed - not good when there are over a
| thousand payment per day
|
| Any Ideas ?? (there "has" to be a way to do this)
|
| --
| Wayne
| Manchester, England.
|
|

 

[Thomas A. Rowe]

Have you considered using your server's date and time instead of Access, and then passing to PayPal
a order/tracking number so that you can always match the payment?

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
http://www.Ecom-Data.com
==============================================

Hi Stefan

I have tried this

If you are getting the data from PayPal as say DateTime convert it before writing it to the DB

But I can't see how to do this (I think it can't be done)
01/11/2009 could be 11/01/2008
I can use DatePart to extract the segments and "re-do" them but which part
do I "re-do". They could both be correct.

The lines I am going down at the moment (I understand it's a little mad -
but can't think of anything else) it to assume that inputs were always made
within the last week (we import daily except for weekends). If the timestamp
is
01/11/2009 and today is 13th January 2009 I can write an update on import no
problems and convert to 11/01/2009 - but thats all I can think off at the
moment. This will only fail during the chritstmas period when imports are
stopped for 10 days

Maybe I need a coffee to make it all work

So in ASP, Now() will always be your server date/time

I am only slightly just getting into server side scripts ( just got
expression web - and running though a new on-line booking system to go live
this december with that). So I will keep your answer and try and bring this
into the form design for the new setup.

Many thanks - that seems to be the way forward





--
Wayne
Manchester, England.

Client side script will always load/render the users time zone / loc settings
Server side script will always use your hosted server location time zone but render it in browser
based on the users local settings

So in ASP, Now() will always be your server date/time

If you are getting the data from PayPal as say DateTime convert it before writing it to the DB

<%
MyDate= (Month(DateTime)&"/"&Day(DateTime)&"/"&Year(DateTime)
%>
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|I have posted this to both the Access forum and the Frontpage forum
| ____________________________________
|
| Hi
|
| Is anyone using a website with an access DB with a time stamp - if you have,
| how have you got round the time stamps being in different formats.
|
| Driving me mad this one.
|
| Yesterday we got a large number of payments from the UK and Peru (we have an
| agency in Lima)
| The access DB has a timestamp formatted Time/Date
|
| But this of course stamps the "local" time/date
| UK = 13/06/2008
| Peru = 06/13/2008
|
| I use the timestamp to validate the payment through PayPal - it's the "only"
| non user input that we get on both the PayPal statements and the user input
| form (to the on-line DB) so there is nothing else I can use as this is the
| only data thatâ?Ts the same on both streams. Everything else may or may not be
| correct â?" ie. E mail addressâ?T are typed and so sometime wrong on one or the
| other (there is no link from the form to paypal so I canâ?Tt validate this).
| The same goes for the personâ?Ts name (yes people spell their names wrong).
| Etc. etc. There is only the timestamp to use.
|
| I have tried setting the timestamp to a simple Now() - to force it to UK
| format but all this does is load the local time (set from the users computer)
| which is based on the regional settings of the machine being used to input
| the data.
|
| I "thought" I could code virtually anything in access but this has me
| beat. I have tried using CDATE but this fails on 01/12/08 and 12/01/08 (as
| they are both correct).
|
| I have tried importing the timestamp from outlook as it's received but this
| also fails 01/12/08 (and any other combination that "could" be correct)
|
| I have tried using my local server timestamp to update AfterUpdate (but you
| still get the "local" time/date
|
| So, unless everyone in the world would like to move to London then I need to
| fix this. At the momnet we are importing the DB and simply looking at the
| date to see what needs to be changed - not good when there are over a
| thousand payment per day
|
| Any Ideas ?? (there "has" to be a way to do this)
|
| --
| Wayne
| Manchester, England.
|
|