8.0.2 update problems

Report · Apr 03, 2007

Have updated to DW 8.0.2 and all original scripts in "advanced" record setup fail. Have managed to fix all text and numeric searches by deleting ' and setting as text/numeric but dates declarations will only show the recordset when set to numeric with surroundng #'s.
SQL:
SELECT *
FROM Qry_EnquiryList
WHERE EnquiryID like varID AND Project like %varProject% AND Address like %varAddress% AND Company1 like %Company% AND Status like varStatus AND Estimator like varEstimator AND Received > #varReceived#

When the page is put to the website it fails with:

Application uses a value of the wrong type for the current operation.

Anyone else had thsi problems? My original scripts have been live for over a year without problems.

Report · Apr 03, 2007

Try #%varReceived%#

"Paul Scullion" <webforumsuser@macromedia.com> wrote in message
news:eutq04$o6f$1@forums.macromedia.com...
> Have updated to DW 8.0.2 and all original scripts in "advanced" record
> setup
> fail. Have managed to fix all text and numeric searches by deleting ' and
> setting as text/numeric but dates declarations will only show the
> recordset
> when set to numeric with surroundng #'s.
> SQL:
> SELECT *
> FROM Qry_EnquiryList
> WHERE EnquiryID like varID AND Project like %varProject% AND Address like
> %varAddress% AND Company1 like %Company% AND Status like varStatus AND
> Estimator like varEstimator AND Received > #varReceived#
>
> When the page is put to the website it fails with:
>
> Application uses a value of the wrong type for the current operation.
>
> Anyone else had thsi problems? My original scripts have been live for over
> a
> year without problems.
>

Report · Apr 03, 2007

Thanks for your suggestion, afraid it gave the following error on Test:
Syntax error ..................... AND Received > #'r/01/1901%'# - where the 'r' is subscript and appears to have replaced %01

SQL

FROM Qry_EnquiryList
WHERE EnquiryID like varID AND Project like %varProject% AND Address like %varAddress% AND Company1 like %Company% AND Status like varStatus AND Estimator like varEstimator AND Received > #%varReceived%#
ORDER BY varSort ASC

Report · Apr 03, 2007

I should have looked at my online docs... datevar = '12/31/98'

try: '%varReceived%'

no #s used.

"Paul Scullion" <webforumsuser@macromedia.com> wrote in message
news:eutvfn$21p$1@forums.macromedia.com...
> Thanks for your suggestion, afraid it gave the following error on Test:
> Syntax error ..................... AND Received > #'r/01/1901%'# - where
> the
> 'r' is subscript and appears to have replaced %01
>
> SQL
>
> FROM Qry_EnquiryList
> WHERE EnquiryID like varID AND Project like %varProject% AND Address like
> %varAddress% AND Company1 like %Company% AND Status like varStatus AND
> Estimator like varEstimator AND Received > #%varReceived%#
> ORDER BY varSort ASC
>

Report · Apr 04, 2007

Thanks again for responding.

With the variable set as a Date and using '%varReceived%'
generates "Syntax error in query expression"

If I use:
................ AND Received > varReceived

with Declaration:
varReceived
Date
Request("Received")
01/01/1901

On "Test"
Error Report:
[Microsoft][ODBC Microsoft Access Driver Data type] mismatch in criteria expression
but works fine when published

It beats me I cannot afford to rely on testing complex scripts "live" when the Test should be doing it for me, so may have to return to DW v8.0.0

Any other ideas would be helpful

Report · Apr 05, 2007

There are flaws in the ASP code that DW generates for communicating with a
SQL server. I've had to go in and manually correct it so that it works many
times. You might try looking at it carefully.

Other than that, I don't know why it's not working for you.

Good luck.

"Paul Scullion" <webforumsuser@macromedia.com> wrote in message
news:ev0o15$ish$1@forums.macromedia.com...
> Thanks again for responding.
>
> With the variable set as a Date and using '%varReceived%'
> generates "Syntax error in query expression"
>
> If I use:
> ................ AND Received > varReceived
>
> with Declaration:
> varReceived
> Date
> Request("Received")
> 01/01/1901
>
> On "Test"
> Error Report:
> [Microsoft][ODBC Microsoft Access Driver Data type] mismatch in criteria
> expression
> but works fine when published
>
> It beats me I cannot afford to rely on testing complex scripts "live" when
> the
> Test should be doing it for me, so may have to return to DW v8.0.0
>
> Any other ideas would be helpful
>

Report · Apr 06, 2007

The Dreamweaver 8.0.2 updater introduced bugs with parameters in all server
models. If the live page works, continue to work with it in code view and
don't update using the dialog boxes any more.

Tom Muck

"Paul Scullion" <webforumsuser@macromedia.com> wrote in message
news:eutq04$o6f$1@forums.macromedia.com...
> Have updated to DW 8.0.2 and all original scripts in "advanced" record
> setup
> fail. Have managed to fix all text and numeric searches by deleting ' and
> setting as text/numeric but dates declarations will only show the
> recordset
> when set to numeric with surroundng #'s.
> SQL:
> SELECT *
> FROM Qry_EnquiryList
> WHERE EnquiryID like varID AND Project like %varProject% AND Address like
> %varAddress% AND Company1 like %Company% AND Status like varStatus AND
> Estimator like varEstimator AND Received > #varReceived#
>
> When the page is put to the website it fails with:
>
> Application uses a value of the wrong type for the current operation.
>
> Anyone else had thsi problems? My original scripts have been live for over
> a
> year without problems.
>

Report · Apr 20, 2007

Thanks to Tom & Tea Rust for offering suggestions. This seems to confirm that I need to return to version 8.0.0 until Adobe fix the bugs they have introduced. I do not find it acceptable to have to hand code in "Code View" mode. This defeats the object of buying a "sophisticated" html editor.

I suspect that the next upgrade will receive a cool reception!

Report · Apr 20, 2007

Don't know about cool reception. Some are upset about what's been left out
in the development side, others on Macs seems to have issues with
performance, and non-USA pricing is quite heated.

But as usual, you have to realize more people will voice/write their
complaints than their positives.

For myself, I haven't yet purchased the software. Definately won't until
actually seeing the trial. Based on just what is written on Adobe's site,
I'm not overly impressed with the bang for the buck on this release.

I highly doubt I will be upgrading at home. Just too expensive for a hobby
site. Will probably end up buying Microsoft's Expression software.

"Paul Scullion" <webforumsuser@macromedia.com> wrote in message
news:f0akbq$il8$1@forums.macromedia.com...
> Thanks to Tom & Tea Rust for offering suggestions. This seems to confirm
> that I
> need to return to version 8.0.0 until Adobe fix the bugs they have
> introduced.
> I do not find it acceptable to have to hand code in "Code View" mode. This
> defeats the object of buying a "sophisticated" html editor.
>
> I suspect that the next upgrade will receive a cool reception!
>