Hello Everyone, I ran into this problem, and only seem to be happening with a new site I've created. I uses PHP/MYSQL, working remotely and uploading to the server setup. When I create a database connection, no problems. From the connections tabs I can navigate the db schema. But when I create a recordset for binding, I get a "HTTP Error 403 Forbidden" message. No problems with viewing the tables and the columns in the recordset setup, but trying to "test" via the button, or navigate the recordset via the binding tab, I have problems. help? Anyone run across this, and if so, how did you fix it. Thank you, tom
I hate when someone posts a question, and then replies to their own question with only something like, "found it, thx!", and no real follow-up. So, I'll say: Found it, thx, too, but tell you what I did to get rid of it. It seemed when DreamWeaver moved the _MMScripts folder up, a permission must have not been set correctly (guessing in hind sight here). So, in my testing, I deleted the MM scripts folder and moved the directory up via an FTP program. It appears like I can navigate the information via the binding folder now. Can't live without my 'click-and-drag' world. Thanks everyone who took the time to try and figure this out! Tom
I have the same problem but when move the folder up from testfolder\_mmscripts to \_mmscripts it just makes a new one in testing and same problem.
Wow this was a while ago. I had the same problem again, about a month or two ago. I had to keep asking questions from my hosting company, and after the 'trouble ticket' was upgraded, I was immediately told what happened. I new 'filtering' system was blocking remote access via dreamweaver. MySQL, PhpAdmin, and such had not problem, but DW was blocked. They provided me code to add to .htaccess, and I then had no problems. So I suggest you contact your hosting company, and push the issue, explain you are using remote access via DW. later, tom
The code I was given was: 1. Specific to the type of "filter" they put in. and 2. Bypassed server security. So, you need to generate a trouble ticket explaining your problem. later, tom