There could be a difference in JET service pack, or the date formats in
Regional Options (in the Windows Control Panel).
There is no need to parse this value though. Assuming that Do_Date is a
date/time field (not a text field), just assign the date. Or if you are
trying aiming to get the 1st of the month, you could use:
SELECT DateSerial(Year ([othTABLE].[Do_Date]),
Month([othTABLE].[Do_Date]), 1) AS Expr1, ...
BTW, you reallly, desperately need to apply some service packs to these
A2000 installations. SP3 will take you up to 9.0.6620. And you need to apply
at least SP7 (preferably sp8) for JET 4 as well. Both are available in the
Downloads from support.microso ft.com. IMHO, A2000 without the service packs
is actually unusuable.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"sean" <se******@hotma il.com> wrote in message
news:10******** *************** ***@posting.goo gle.com...
Hi All,
I have one table TABLE1 in access2k on machine PC1, that has one
column named DO_DATE with "Date/Time" data type. Two other machines
PC2 and PC3 also running access2k. Each PC has its own data entry
form, and each form would execute the following insert query
independently:
INSERT INTO TABLE1 (DO_DATE, ... )
SELECT DatePart("m",[othTABLE].[Do_Date]) & "/" &
DatePart("yyyy" ,[othTABLE].[Do_Date]) AS Do_Date, ...
FROM othTABLE ...etc
My results:
PC1 would always insert correctly (ie, 01/12/2004);
PC2 would always insert NULL !!!
Question:
All the machines were installed with the same version of Access2k, ie
(9.0.2720); why same insert query on different machine could result
differently ?
Thanks
sean