[AccessD] Dynamic SQL statement

Stuart McLachlan stuart at lexacorp.com.pg
Mon Dec 7 17:19:36 CST 2015


Doh!  That's the trouble with starting from a pre-conception.

A DAO solution is probably easier than SQL in this situation.

-- 
Stuart


On 7 Dec 2015 at 17:31, Susan Harkins wrote:

> Oh my... now that is easier isn't it -- and if a control's empty, does
> it throw an error? I'm afraid my mind always turns to SQL and maybe
> that's not a good thing. :)
> 
> I have the day off tomorrow -- it's inauguration day here in Kentucky
> for our newest Governor. I'll try it out on Wednesday. Thank you.
> 
> Susan H.
> 
> On Mon, Dec 7, 2015 at 5:11 PM, Bob Walsh <BWalsh at acumentra.org>
> wrote:
> 
> > How about...
> >
> >         Set rs1 = CurrentDb.OpenRecordset("Exam", dbOpenDynaset,
> > dbAppendOnly)
> >         rs1.AddNew
> >         rs1!IndividualIDFK = ctl.Column(2, varItem)
> >         rs1!ExamDescriptionIDFK = strExamType
> >         rs1!ExamDate = strExamDate
> >         rs1!Results = strObservation
> >         rs1!NextExamDue = strFollowupDate
> >         rs1.Update
> >         rs1.Bookmark = rs1.LastModified
> >
> >         rs1.Close
> >         Set rs1 = Nothing
> >
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 




More information about the AccessD mailing list