Art wrote:
> I've been digging into my page and reapplying the stored
procedures and
> for some reason, it now works without any manual
addition. I can't say
> whether it's an Adobe or Webassist that fixed it. The
other day, when I
> applied the DB Search, I think that's what I was working
on, it might
> have been just editing the ecart but I got a message
that said something
> like " cursor wrong type ...applied to page" When I
uploaded it on the
> test server, it suddenly worked fine without the edit.
Problem solve but
> I'm not sure who solved it or when.
Its working, so thats all good!
> However, I did find out from Webassist, after submitting
a support
> ticket, that DB Search does NOT support stored
procedures. I've had to
> revert back to using a standard recordset instead. Not a
big deal.
>
> There was also a bug in it and they told me that for
complex queries,
> where you have more than one table with the same column
name, DB Search
> isn't able resolve which table to use. A manual edit was
needed.
> However, every time you click into the DB Search and
edit search
> criteria, it reverts back. So, instead of having
"tablename.ID", it
> reverts back to "ID" So every time you edit it, you have
to manually add
> the tablename. Also not a big deal but they have logged
it for correction.
I am going to be trying to create an advanced text search
using stored
procedures, but first I need to see what a recordset based
one looks
like, and then try to use that code directly in a stored
procedure. My
current stored procedure is huge, it allows for 4 levels of
filters, any
of which can be null, and the text search. This will all be
implemented
in v2 of my project, but thats not scheduled to start for a
while.
Once I do have the advanced text search cracked, I will post
an example
here for you.
Steve