How can i change autocomplete-index-php-1.php file so it support mysqli recordset?

I'm using PHP5.6 and Mysql5.5

Hello p k,
The extension was created years ago, supporting the built-in Dreamweaver Server Behaviors. Currently we do not support MySQLi as it is not natively supported in DW.
There is an updated version of this extension coming soon - it will support HTML5 Data Bindings and DMXzone Database Connector (which are PDO-based)

When is the new version coming out please?

My website now produces an ugly error to the world in a bright red dialog box whenever someone tries to use Autocomplete:

Start of error shows:
mysql_pconnect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in...

Why couldn't you have warned us this would happen to our websites instead of letting us find out ourselves, or worse as in this case - through customers?

When is this product going to be updated to handle mysqli , at this point after 2 years of it not being available beginning to feel ripped off, why would we even look at wappler , when this is the level of support DMXzone is known for providing.

Hello,
As i explained this in the topic and as i explained this to you personally a couple of times already, this product was released about 10 years ago, when the DW server behaviors were actual and up to date. The product was developed especially to be used with DW server behaviors and it relies on the server behaviors code. The errors about mysql_pconnect() are produced by the DW server behaviors code, which the extensions rely on, and when the newer PHP versions do not support the server behaviors code, there is nothing we can do to change the code DW produces. That is the reason Adobe removed the server behaviors from DW - as they are producing outdated code, which cannot be used on PHP 5.6+

A new autocomplete extension, based on server connect and dmxzone database tools, which are based on PDO (much better than mysqli) is in our roadmap. You will be notified as soon as it is available.

As for Wappler, it is up to you to choose whether to continue using the outdated technologies present natively in DW, or switch to a modern, faster platform which always generates up to date code and cutting edge technologies. Hundreds of designers and developers already joined Wappler during our crowdfunding campaign, hundreds more were invited in the beta community - the feedback is really great already, even though the product is still in beta version

"A new autocomplete extension, based on server connect and dmxzone database tools, which are based on PDO (much better than mysqli) is in our roadmap" This over 2 years old now we've been hearing this.

My fear with DMX Zone products is its always only a beginning to having to spend large sums of money since most of your products do just small bits of a solution and am always being asked to spend more for little things that make sense to be included anyways. So no not buying into Wappler because I fear its just a money drain being created by DMXzone.

That's your choice and you can continue using a product with no future, which will soon be abandoned by Adobe.

As for the "small bits of solution" - you cannot expect something to be included somewhere, if it is not described as a feature on the product page.
If these are such small things - you could always hand code them, and not rely on extensions.
Have a great day.