Andy Lacey
andy at minstersystems.co.uk
Sat Apr 12 10:04:02 CDT 2003
Darren You don't have to use ADO if you don't want to. You just have to dim your objects specifically as DAO ones (or, I believe, open the list of references and move DAO up to above ADO in whch case it becomes the default). After that you can go on using DAO same as ever. Andy Lacey http://www.minstersystems.co.uk > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darren DICK > Sent: 12 April 2003 16:00 > To: accessd at databaseadvisors.com > Subject: Re: [AccessD] A2K: OpenRecordset doesn't > > > Thanks to all who replied. > > I went to the (not) Help and am now using some > plagiarised code directly for ADO > It seems to work > > Thanks Susan and Andy > > > > ----- Original Message ----- > From: "Susan Harkins" <harkins at iglou.com> > To: <accessd at databaseadvisors.com> > Sent: Sunday, April 13, 2003 12:51 AM > Subject: Re: [AccessD] A2K: OpenRecordset doesn't > > > > > > Well, you don't need the ; at the end of the SQL > statement, but don't know > > that it's your problem. > > > > Susan H. > > > > > > > Can anyone shed some light on why my code > fails on > > > the line... > > > Set rst = dbs.OpenRecordset("SELECT * FROM > > > tblMyTable;", dbOpenDynaset) > > > and I get the error "Run time error 13 'Type > > > Mismatch" > > > > > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > > http://databaseadvisors.com/mailman/listinfo/acces > sd > > Website: http://www.databaseadvisors.com > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/a> ccessd > Website: > http://www.databaseadvisors.com >