[AccessD] Problem converting code

DAO 3.51 really doesn't work with A2K and later because they are built
on DAO 3.6.

Charlotte


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Clark
Sent: Thursday, January 05, 2006 10:48 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Problem converting code


I tried this first, thinking, "newer may be better," but I got the same
thing, so I set it to exactly what was in my A97.

>>> wdhindman at bellsouth.net 1/5/2006 12:32 PM >>>
...I'd use DAO 3.6 instead of 3.51 in A2K and above ...as for the
tblMain 
bit, have you decompiled the code as yet?
...if that doesn't do it and you don't have a decent search tool (Access
is 
a bad joke as far as searches) like Speed Ferret then take a look at
your 
form event properties and data sources ...I put as much there as I can
to 
avoid form code modules when possible but pre A2K3 Access searches
usually 
won't find them.

William

----- Original Message ----- 
From: "John Clark" <John.Clark at niagaracounty.com>
To: <accessd at databaseadvisors.com>
Sent: Thursday, January 05, 2006 12:00 PM
Subject: Re: [AccessD] Problem converting code


>I figured it was something like this, but I added the reference to
ADO
> 3.51, which is what is in A97, and made sure it was above ADO, but
it
> still gives me an error on that line, saying that there are "Two few 
> parameters. Expected 1." Now, when I first tried using this, I was 
> getting "can't find tblMain" which isn't even in the code anywhere 
> that I can find.
>
>>>> wdhindman at bellsouth.net 1/5/2006 9:31 AM >>>
> ...and don't forget to set the DAO reference higher in the list than 
> the ADO reference ...or remove the ADO reference altogether.
>
> William
>
> ----- Original Message -----
> From: "Bryan Carbonnell" <carbonnb at gmail.com>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Sent: Thursday, January 05, 2006 9:21 AM
> Subject: Re: [AccessD] Problem converting code
>
>
>> On 05/01/06, John Clark <John.Clark at niagaracounty.com> wrote:
>>
>>> The bigger problem though is that this was done in A97 and I am
now
>>> using A2K. I will be redoing this program in A2K and the program I
> am
>>> currently working on and trying to reuse the code in, is also A2K.
I
> am
>>> getting errors on the line, "Set rst =
> CodeDb.OpenRecordset(strSQL)"
>>> that says too few parameters. I am either being totally dense (a 
>>> distinct possibility) or it is a DAO vs. ADO problem, which I can
> not
>>> get through my skull and always have problems with...making me
> dense
>>> again...hmmmm.
>>
>> It appears to be DAO code, so you will need to add a reference to
> DAO.
>> A2K defaults to ADO.
>>
>> --
>> Bryan Carbonnell - carbonnb at gmail.com
>> Life's journey is not to arrive at the grave safely in a well
>> preserved body, but rather to skid in sideways, totally worn out,
>> shouting "What a great ride!"
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com 
>> http://databaseadvisors.com/mailman/listinfo/accessd 
>> Website: http://www.databaseadvisors.com 
>>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd 
> Website: http://www.databaseadvisors.com 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd 
> Website: http://www.databaseadvisors.com 
> 


-- 
AccessD mailing list
AccessD at databaseadvisors.com 
http://databaseadvisors.com/mailman/listinfo/accessd 
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com