Re: Re: ODBC
| From: | Scott Fletcher | Date: | Wed, 07 Aug 2002 14:40:45 +0000 |
| Subject: | Re: Re: ODBC | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-111507@lists.php.net to get a copy of this message | ||
Hi Andrew!
One quick correction! I did have success with it for a year and a half!
It just cause more problem than what it should be. The tech support at
OpenLink have been very helpful and I like that. But this wasn't the reason
I decide to let go of the OpenLink. There are a few things here!
1) Data type conversion between PHP and MS-SQL through OpenLink is a bit
different. The biggest fault lie with MS-SQL on this one. I guess it must
have to do with the competition reason, doesn't MS love to squash the non-MS
softwares. A helpful solution but not a very effective solution was to have
the MS ODBC driver set up on the MS-SQL Server where the Unix sever using
OpenLINK then point to MS ODBC driver then MS ODBC point to the MS-SQL
Server.
2) We have internet network IP address changes a couple of time due to
my company moving to a different location and later with the ISP change and
later with a new firewall. When it become so long, I forget that MS SQL
server on Win2000 would have to be rebooted because Win2000 doesn't actually
change the IP address from the bottom up. I end up spending a few days
troubleshooting the problem because OpenLink could not communicate with
MS-SQL Server. I'm kind of surprised that the OpenLink software on Win2000
didn't get that message.
3) We have a knowledge base and we noticed one problem with it! The
problem if there is a very long comments in just one row, one field, the
database, MS-SQL can show it all but OpenLink won't show it all, so the
comments end up being cropped off at the end. I get lot of complaining from
the customers as well as the staffs. As result of keeping in touch with the
OpenLINK tech support, they told me that OpenLINK design the software to be
a little bit more strict in handling the data. So, it was an internal
matter at OpenLINK.
I had to make a decision because my company will move in a year and
soon, the machine will go offsite. I just can not handle it anymore so I
junked it and move the website to Windows. Yea, we had to buy a window
machine for that. The problem is some people where want Windows and some
other want UNIX or Linux. Can't have it both way. The bad thing is the
staff do not wish to have the webserver installed on the MS-SQL server. So,
I just can not handled it anymore because it is taking my time away from
projects I'm working on.
It is nothing personal. Just that compactibility difference is more
trouble than what it's worth.
Scott
"Andrew Hill" <ahill@openlinksw.com> wrote in message
news:030001c23e18$81aad930$eb0ba8c0@usnet.private...
> Hi Scott,
>
> I'm sorry to hear you experienced problems with this architecture.
> Free support is always available for OpenLink products at
> http://www.openlinksw.com/support/suppindx.htm.
>
> I am also extremely surprised that you worked on this for a year and a
> half without success. Our ODBC agent in our Multi-Tier driver works
> exceptionally well for this situation, and any OpenLink support person
> as well as many people on this list could have provide quick assistance.
>
>
> If you do require any help in configuring drivers with PHP, please don't
> hesitate to ask.
>
> Best regards,
> Andrew Hill
> Director of Technology Evangelism
> OpenLink Software http://www.openlinksw.com
> Universal Data Access & Virtuoso Universal Server
>
> -----Original Message-----
> From: Scott Fletcher [mailto:scott@abcoa.com]
> Sent: Friday, August 02, 2002 3:25 PM
> To: php-general@lists.php.net
> Subject: [PHP] Re: ODBC
>
> Yes! Unfortunately, you'll have to install the special driver on the
> Linux/Unix becuase of the communication difference between UNIX &
> Windows as
> well as the language difference between these two. I tried using iODBC
> and
> openLINK. After 1 1/2 years, I decided that open source code for this
> is no
> good because they are not compactable and it is such a big, big pain in
> the
> butt!!! So, I ended up moving the website on UNIX to windows. Why,
> because
> of the way the data type is being coverted between 2 platform and
> character
> length or type is strictly limited. I have not tried to buy such a $600
> or
> $800 driver software to see how well it does because it is a waste of
> money
> and MS kept changing the programming in the MS Access and MS SQL making
> the
> drivers useless.
>
> "Ashley M. Kirchner" <ashley@pcraft.com> wrote in message
> news:3D4AD0B1.ABEE0A22@pcraft.com...
> >
> > Can PHP be used on an Apache server (linux) to connect to a
> (remote)
> MS
> > Access server (NT) through ODBC? If so, does anyone have examples of
> how
> this
> > is done? And if not, what other choices do I have?
> >
> > --
> > W | I haven't lost my mind; it's backed up on tape somewhere.
> >
> +--------------------------------------------------------------------
> > Ashley M. Kirchner <mailto:ashley@pcraft.com> .
> > 303.442.6410
> x130
> > IT Director / SysAdmin / WebSmith . 800.441.3873
> x130
> > Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave.
> #6
> > http://www.pcraft.com ..... . . . Boulder, CO
> > 80303,
> U.S.A.
> >
> >
> >
>
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>