Finally wanting to convert to Mysqli, but ...

... the local server I am using (MAMP Pro) only has Mysql options, nothing with Mysqli. Will that be a problem? I heavily rely on local testing before putting pages online.

My profile shows I am up to date with Design extender and eCart. So I will be getting Data Bridge v2 and MySQLi Server Behaviour. Will I be all set with that?

Thanks in advance :)

Bought the extensions. Updated the data connection, but when I test it, I get the error message in the screen shot. Going back to the original pages, I get the same error code.

This is an issue with your Dreamweaver site definition. Usually it is a bad site URL setting. I'd have to see your connection information to be sure, but look at the testing server settings and make sure they are all correct. If you can't spot the issue then I may need you to send me your site definition export so I can re-create the problem from here.

I can't spot the mistake.

We could do a ticket. I'd start by uninstalling and reinstalling WAMP. You won't be able to connect to a database that won't start in the first place. Just call the number at the bottom of every webassist page to schedule a screen sharing session to look into this further, or post your phone number and I'll call you.

A little progress with MAMP instead of MAMP PRO

It looks like your localhost server is running php7 and your site is still using standard MySQL. You might want to use php6 until your site is fully converted.

I change php version and was able to connect to the local server. I will try converting a file to MySQLi over the weekend. Is there a tutorial for existing pages to convert them?

You just have to:

1) Create a MySQLi connection
2) open each Recordset, Insert, Update, and Delete server behavior and choose the new connection and click "ok"

Hi Ray, with the help of the extension I switched some of the pages over to MySQLi, some however are giving me trouble. Should I post them one by one, or should we do them all in a screen sharing session?

Error messages include:
- Error: the object is not currently contained in a document
- No data supplied for parameters in prepared statement
- Commands out of sync; you can't run this command now

The last two error messages appear under one of the recordset, that is displayed instead of the page.