Ask a Question related to Macromedia Dynamic HTML, Design and Development.
-
per4mance #1
Error after testing Recordset
Hi,
I've a problem with using Recordsets. It's not possible to make an RS. I
choose the database, the table - the Test works fine, after I click 'Ok' I get
the message:
The following JavaSripts error(s) occurred: At line 382 of file
"....Dreamweaver
8\Configuration\ServerBehaviors\Shared\RSSeverMode lSwitches.js" ReferenceError:
FieldTypes is not defiend
What can I do? I use Dreamweaver 8.0.2 on Windows XP SP2 Prof.
Regards from Germany
Thorsten
per4mance Guest
-
recordset error
I have the following recordset: SELECT FTE_CLASS_GROUP_NBR_DSCR FROM dbo.DLIST_FTE_CLASS_GROUP WHERE FTE_GRP_ID IS NOT NULL I ammended the sql to... -
No Testing server error
I am a student trying to learn Dreamweaver MX 2004. I'm trying to setup a PHP page and connect to a MySQL Database. MySQL is running and using the... -
recordset error
I'm opening a recordset that calls a stored procedure and get the following error: 'Operation is not allowed when the object is closed' The error... -
Testing Server Error
Please help... I'm trying to set up a database connection via an IP address and always get this error when testing the database connection: HTTP... -
testing for a null Date in the Filter property of a RecordSet object?
Hello, I am new to using the filter property. When I try publishDate = '' I get a type mismatch error. Any ideas? Thanks Rich -
G-Rex #2
Re: Error after testing Recordset
Thorsten,
I am experiencing the exact issue now after updating to 8.02. Is there a
correlation? Have you had any success in resolving your problem? I notice the
original post was almost 2 months ago. Please share any fix/remedy you may
have discovered.
Thank you!
Gary
G-Rex Guest
-
G-Rex #3
Re: Error after testing Recordset
Problem Solved!
I just deleted my configuration folder in my C:\Documents and
Settings\Username\Application Data\Macromedia\Dreamweaver 8
Dreamweaver rebuilt the Configuration folder when it started. I am sure
someone could narrow the focus to finer detail, instead of killing the whole
folder. But for now it is back up and running.
:grin;
G-Rex Guest



Reply With Quote

