[AccessD] ADO Problem

Hello Rocky,

Is that MS Access BE, which is used with ADO? - then this should work:

   conn.Execute "INSERT INTO tWeeklyUpdateSent ( DateSent ) " & _
                 "SELECT " & CLng(dtToday)


--
Shamil
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Beach Access
Software
Sent: Tuesday, November 28, 2006 10:36 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] ADO Problem

Using:

"SELECT #" & dtToday & "#"

He gets an error message: 

Invalid column name '#11'

dtToaday does contain 11/28/2006

What else could it be?

MTIA

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of McGillivray, Don
[IT]
Sent: Tuesday, November 28, 2006 10:39 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] ADO Problem

Hi, Rocky.  

Just a WAG (I don't know ADO), but how 'bout:

   Conn.Execute "INSERT INTO tWeeklyUpdateSent ( DateSent ) " & _
                 "SELECT #" & dtToday & "#;" 

Don

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Beach Access
Software
Sent: Tuesday, November 28, 2006 10:15 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] ADO Problem

Dear List:

A colleague (who thinks I know ADO) writes in to ask why the following:

   Conn.Execute "INSERT INTO tWeeklyUpdateSent ( DateSent ) " & _
                 "SELECT " & dtToday & ""

Inserts a record into tWeeklyUpdateSent so the conection is OK.  But but the
date is 1/1/1900 instead of today's date.

I had him check the contents of dtToday and it does indeed have 11/28/2006
in it.

Does anyone see what he's doing wrong here?


MTIA

Rocky