[AccessD] Parameter Queries via Code

SCARY stuff!

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Admin Sparky
Sent: Friday, April 29, 2005 3:40 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Parameter Queries via Code


*** SOLVED *** (but don't ask why)

You are not going to believe this one!  I've had a continual search going on
all day for what may be the problem.  I finally found a cached page from a
google search from someone who had my exact "symptoms".  It turns out that
his DAO reference had migrated below his Excel reference and after
re-ordering his references everything worked.  Now, in my case my DAO
reference was already ahead in the order, but I figured "what the heck" it
may just be a flaky reference, so I re-ordered them, then re-ordered them
back again.

Now everything works using Charlotte's original syntax.  Whoohoo!

Mark Mitsules



On 4/29/05, Admin Sparky <dba.email at gmail.com> wrote:
> You know...this happened to me once before...going 'round and 'round 
> on a problem till it was pointed out that what I was attempting 
> couldn't be done with a totals query.  As it happens, this IS a totals 
> query...could that be the problem?
> 
> Mark Mitsules
> 
> On 4/29/05, Gustav Brock <Gustav at cactus.dk> wrote:
> > Hi Mark
> >
> > If none of these work, your SQL must be pretty strange.
> >
> > You may have to bring it forward ...
> >
> > /gustav
> >
> > >>> dba.email at gmail.com 04/29 9:04 pm >>>
> > These each produce data type mismatch errors.
> > qdfMetrics.Parameters(0) = 1., 2., or 3.
> >
> > 1. Forms!frmDatePicker!Text14
> > 2. "#" & Format(Forms!frmDatePicker!Text14, "m\/d\/yyyy") & "#" 3. 
> > DateValue(Forms!frmDatePicker!Text14)
> >
> > In an online example that I saw, they used the following: Dim prm As 
> > Parameter For Each prm In qd.Parameters
> > prm.Value = Eval(prm.Name)
> > Next prm
> >
> > This method hasn't worked either...same error message.
> >
> > I can't remember exactly how the quote goes...something like "I must 
> > be closer to the solution, because I've just discovered another way 
> > it won't work".
> >
> > Mark Mitsules
> >
> > --
> > 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