"Matt" <Matt@[EMAIL PROTECTED]
> wrote in message
news:9DCE0A61-0696-4BB2-8855-866E66BE1AAB@[EMAIL PROTECTED]
> Brendan,
>
> Unfortunately, I wasn't lucky enough to have made that mistake. I did
> have
> the columns set to date/time format. I did some playing around and
found
> a
> work around. Access stores date/time in double integer format. It just
> converts the number to a date/time when it displays it. So, with that
in
> mind, I converted all of my date/time columns in the SharePoint list to
> number columns and it worked!
>
> The only drawback is that SharePoint will only display it in the raw
> number format. So, if you plan to manipulate the date/time data in
> SharePoint, this probably isn't the solution. But, if you are stricktly
> using the data in Access, this did the trick!
Matt, I just tried a test. I created a list in SharePoint and added a
date/time column, set to allow a time part. I linked to that list in
Access
2007, created a form bound to that list, and added a command button to the
form with the following line of code:
Me.TestDate = Now()
TestDate is the name of a text box bound to the date/time column, also
called TestDate, in the linked SharePoint list.
It works, successfully assigning the current date and time, without any
error.
I can't say what the cause of your problem is, unfortunately, but as far
as
I can see it is possible to assign a date to a SharePoint date/time column
from Access, and it should not be necessary to change the type of the
SharePoint column to Number.
--
Brendan Reynolds
|
