Alright. I've been working with ASP for a long time and with the tools built
into Dreamweaver 8 (and previous versions) it's simple to connect my ASP pages
to an ODBC connection for creating recordsets and executing commands. But I've
finally accepted the fact that I need to learn to develop in PHP. I've got PHP
running on my machine and I'm able to hand code connections to an ODBC data
source but I'm curious how to get the Recordset creation wizard and the Command
creation wizard to connect to anything but a mySQL table.

And for those of you who are going to tell me to just switch my data to mySQL,
that's simply not an option.

Thanks in advance for any help you can provide.

derfiticulum wrote:
> Alright. I've been working with ASP for a long time and with the tools built
> into Dreamweaver 8 (and previous versions) it's simple to connect my ASP pages
> to an ODBC connection for creating recordsets and executing commands. But I've
> finally accepted the fact that I need to learn to develop in PHP. I've got PHP
> running on my machine and I'm able to hand code connections to an ODBC data
> source but I'm curious how to get the Recordset creation wizard and the Command
> creation wizard to connect to anything but a mySQL table.
>
> And for those of you who are going to tell me to just switch my data to mySQL,
> that's simply not an option.

Dreamweaver's built in PHP server model is not designed to connect to any other database than MySQL, so I'm afraid that the answer is to convert to MySQL, or to hand code all of your database interaction, that is you won't be able to use the Dreamweaver recordsets to connect to MySQL (and therefore won't get any data bindings either). I've not done the later anytime recently, so can't provide any particular tips on that, except perhaps to search for PHP ADODB.

If you're using Access as your database, then perhaps this search can help with a conversion if you ever do want to go that route:
http://www.google.com/search?hl=en&q...ccess+to+MySQL


--
Danilo Celic
| http://blog.extensioneering.com/
| WebAssist Extensioneer
| Adobe Community Expert

danilocelic AdobeCommunityExpert wrote:
> Dreamweaver's built in PHP server model is not designed to connect to
> any other database than MySQL, so I'm afraid that the answer is to
> convert to MySQL, or to hand code all of your database interaction, that
> is you won't be able to use the Dreamweaver recordsets to connect to
> MySQL (and therefore won't get any data bindings either).

Just to add to Danilo's comments, the problem is that PHP originally
developed a different set of functions to communicate with each type of
database. So, you have different functions for MySQL, MS SQL Server,
Oracle, PostgreSQL, etc. Yes, it's crazy, but that's how the language
originally developed.

PHP 5 introduced PHP Data Objects (PDO), which are database-neutral.
Unfortunately, Dreamweaver's PHP server model dates back to 2002,
several years before the introduction of PDO. InterAKT, a Romanian
company that was acquired by Adobe a couple of years ago, developed a
Dreamweaver extension called PhAKT, which provided ODBC connectivity.
But PhAKT was withdrawn several years ago.

So, the bottom line is use MySQL if you want Dreamweaver to do most of
the heavy lifting for you. Otherwise, you'll need to code everything by
hand. I have been pressuring Adobe to support PDO for the past three or
four years, but it hasn't happened yet.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Well, that's pretty much the answer I was expecting, I guess. I've been doing
this long enough that I know how to write all the sql statements and all that
jazz and I've got a good grasp on all the concepts of what has to happen and
when. I just thought that there might be a quicker way for me to learn the
syntax by having Dreamweaver build the code for me. As far as switching to
mySQL, like I said before, that's not an option. I'm writing some web apps for
some cobol software that use a cobol data variant called "vision data" so
switching data formats isn't an option. I appreciate your confirming my fear.
Now, I've got no choice but to dive in and learn I guess. Thanks again.