Jump to content

Need help in DW8 adding a recordset


Recommended Posts

I am in Chapter 10 of "DW8 with ASP, CF, & PHP" by Jeff Bardzell and have hit a real snag.  I am trying to add a recordset(query)  in the bindings panel.  This brings up the menu where you specify recordset name, connection, and table.  When I do that and run "test", I get an error.  In fact, I got two.  The first one says "mysql error 1054 - unknown column 'colname' in 'where clause'.  This first error message only showed up one time.  the second message is a long message and says "While executing onclick in serverBeh-PHP-simpRS.htm, the following javascript error occurred: 'at line 252 of file C:\.....DW8\configuration\shared\MM\scripts\RecordsetDialogClass.js'  Exception thrown in native function"
It seems to be isolated in one column of one table, exercizeReqd.  All the others work fine when "test" is clicked.  Anybody have any ideas?  This really has me stumped.
Link to comment
Share on other sites

By trial and error I figured this out.  What I ended up doing was changing the TYPE field in one of the rows.  The "bad" type was bit(20).  I changed it to tinyint(20) and everything is working now.  I am not totally positive about this but I believe that bit was replaced with tinyint in the newer version of MySQL.
Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.