> I wasn't aware that you could do stored procedures in MS Access 2000.
> Although I know you can save a query and call it as if it were a
> regular table via ODBC, I don't know of a way to pass that query
> variables. I would need to pass in a few variables for the WHERE
> statement of the query.
It is possible to do "faked" stored procedures with Access.
You fake it by using a view, like so:
CREATE VIEW sp_empbydept AS
SELECT *
FROMemp
WHEREemp.dept_id = [empdeptid]
"Empdeptid" would be the parameter that you would pass into the query from
your cold fusion code.
If you run thi
ner
- Original Message -
From: Eron Cohen <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 23, 2000 2:49 PM
Subject: RE: Query suddenly taking 7 times longer
> Hi Michael,
>
> I wasn't aware that you could do stored procedures in MS Access 2000.
> Al
ent of the query. Is
this possible to do with MS Access? Am I missing something here?
Thanks,
Eron
-Original Message-
From: Michael Imhoff [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 23, 2000 5:21 AM
To: [EMAIL PROTECTED]
Subject: Re: Query suddenly taking 7 times longer
The only th
e Alliance Consulting Partner
- Original Message -
From: Eron Cohen <[EMAIL PROTECTED]>
To: Cf-Talk <[EMAIL PROTECTED]>
Sent: Monday, May 22, 2000 5:53 PM
Subject: Query suddenly taking 7 times longer
> Hi Folks,
>
> "Suddenly" today a SQL query that was takin
Hi Folks,
"Suddenly" today a SQL query that was taking about 20 seconds to perform
last week, is taking 140 seconds to return results. I have no idea what's
gone wrong.
I haven't changed anything on the forms and haven't touched the software on
the server in question recently. When a user exec
6 matches
Mail list logo
