Update to Dreamweaver CS3? Stored Procedures?

Dooza,

By the way, are you a Programmer or Designer first?

I come at this from a Designers point of view so much of this is very
difficult.

I do OK, it just takes so much more time and effort to accomplish stuff.

I rely heavily on the "tools" to help me out but I keep getting requests
for functionality that the tools don't quite do. Add the compatibility
issues and I have a big headache at the end of the week. I keep plugging
on though.

Anyways, see you around.

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.

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 guessing that I added the line after I was happy with the layout of
> the page...its been a while since I made mine.
>
> Steve

Dooza wrote:
> Art wrote:
>> Rowset position cannot be restarted.
>>
>> is the error I get when I remove the offending line...
>
> Is this when you have an item on your page and you add it to your cart,
> or when you add your cart contents to your database?
>
> Steve

I just looked at my code and I too have the additional line for the
cursor type, and I am using stored procedures too.

My recordset looked like it would open, no exclamation mark, but as soon
as I tried Dreamweaver crashed on me.

I am guessing that I added the line after I was happy with the layout of
the page...its been a while since I made mine.

Steve

Art wrote:
> Rowset position cannot be restarted.
>
> is the error I get when I remove the offending line...

Is this when you have an item on your page and you add it to your cart,
or when you add your cart contents to your database?

Steve

Rowset position cannot be restarted.

is the error I get when I remove the offending line...

You use Webassist too? I'm not sure why but when I add a product to
the cart, if I use the new stored procedures, I get an error. I can't
remember the error now but when I add the line to where it sets the
command, it fixes that error. However, the recordset is no longer
visible to Dreamweaver.

When I figured out how to avoid the error, I sort of dropped my search
for a better solution. However, now it's become a problem again because
I can't accomplish what I want. There probably is a solution but it's
avoiding me at the moment. I've thought about going back to the previous
version but that creates problems too.

This whole problem is just so schizophrenic.

Do you use the same username on Webassist?
>
> Why do you need to use the cursor type? Is there a way to avoid it?
>
> Maybe you could go back to the previous version where this wasn't a
> problem?
>
> Steve

Art wrote:
> I use WebAssist and it seems that I can't use part of Webassist until
> this whole "Command" thing is resolved. What a pain.
>
> I've tried creating a recordset using the recordset window but because I
> need to change the cursor type, it disappears. I'm trying to figure out
> a way so that I don't have to change the "Cursor" type (below).
>
> commmname.ActiveConnection.CursorLocation = 3 ' adUseClient
>
> With all the problems with Dev Tools and this, most of my usual tools
> went away when I "upgraded" to CS3. Why did I upgrade, I know there's a
> reason.

I have seen your posts on the WebAssist forums, and I wish a fix was
imminent, I really do.

Why do you need to use the cursor type? Is there a way to avoid it?

Maybe you could go back to the previous version where this wasn't a problem?

Steve

I use WebAssist and it seems that I can't use part of Webassist until
this whole "Command" thing is resolved. What a pain.

I've tried creating a recordset using the recordset window but because I
need to change the cursor type, it disappears. I'm trying to figure out
a way so that I don't have to change the "Cursor" type (below).

commmname.ActiveConnection.CursorLocation = 3 ' adUseClient

With all the problems with Dev Tools and this, most of my usual tools
went away when I "upgraded" to CS3. Why did I upgrade, I know there's a
reason.

OK, thanks.

Art wrote:
>
>
> I haven't been keeping up on this but a while back I had a problem with
> Stored Procedures in CS3. CS3 had a problem with my stored procedures
> and if I tried to use the recordsets created by a command (SP) the
> recordset wouldn't show up and all I would get was a "!" in the bindings
> window. If I wanted to bind data, Dreamweaver wouldn't recognize the SP.
>
> I've been forced to hop back and forth between 8.02 and CS3 if I need to
> work with any of my pages with SPs on them.
>
> Has this been fixed? If not, is there any plan to fix it?
>
> This is especially true since MX collection was shot down in it's prime
> and resurrected as Toolbox.

Still not fixed, the last response from Adobe was it may get fixed in a
future program.

The workaround is to use a recordset instead, then select the stored
procedure from the list at the bottom. There is a small bug here too,
where it only lets you enter one parameter. If you save the recordset
and open it up again it allows you to continue adding as many parameters
as you like.

Steve