🚀 go-pugleaf

> When using Oracle spatial w/ADO you should definately be using
> the proper Oracle OLE DB Provider with a connection string that
> would look similar too:
>
> Provider=OraOLEDB.Oracle;Data Source=this.that.com;User
> ID=user_id;Password=passwd;Persist Security Info=True;DistribTX=0

Ours looks similar too, except we had OraOLEDB.Oracle.1 as our provider.  I
don't know if that would make a difference? Also we had the Persist Security
Info set to False, and we didn't have the DistribTX=0 so I added modified
and added to our connect string but still no joy (btw what does the
DistribTX string do?).

> Look at your connection string to see what provider your using
> with ADO.  http://technet.oracle.com has a specific download
> for OLE DB Provider and I'm almost sure that ADO would not
> understand the spatial column in your table with the correct
> provider.

I'm now downloading the 42mb download from the Oracle site to see if that
sorts out our problem.  I tried to look on the Oracle CD's to see if I had
an update there, but with about 100 CD's scattered about the office finding
the correct one is a bit of a task.  Meanwhile I'm slowing running out of
things I can 'enhance' while I'm stuck on this problem.

> Other than that, I always have the same problem your experiencing
> if I try to use BDE on Oracle tables with spatial columns.

Good to know I'm not the only one!

Thanks for your perseverance.

--

Yours faithfully, Graham Reeds.
grahamr@omnieng.co.uk | http://omnieng.co.uk/