Re: D3 ODBC Problem

"Peter McMurray" wrote:
I think that you will find that D3ODBC is actually a quite good third party
product that they bought because the in house version was not so hot.

I'll preface this all with "to my knowledge", and I welcome
correction. The software which you describe was licensed at an
overall cost in the high 5 figures and I wouldn't be surprised if
someone confirmed the number was well over 6 figures. After all that
I don't believe it was ever used. The ODBC connectivity has always
been the home-grown stuff, so the problems and lack of functionality
present today are of the same category that people were struggling
with almost 10 years ago.

The way the history goes, D3 v8 was supposed to have all sorts of
goodies, including FSI for *nix and the new ODBC client/server. After
going so long with v8 in the pipe but nowhere near close to being beta
quality, RD decided to roll back a lot of the functionality into v7.5.
Not only did this potentially give them the brownie points for
releasing real enhancements in a point-release, but by keeping this a
minor release it allows anyone on a support agreement to get the new
features for free. If they had committed to v8 then people would need
to pay for the update, and considering what's been going on with v7.5
that would have been very bad all the way around. Unfortunately the
new ODBC connectivity was bound to v8, so it was never rolled back to
v7.

The "new" ODBC code is now so old and moldy that I personally wouldn't
have much faith in it. Consider that with all the time that's gone
by, TL would need to get it updated for Vista and W2008 as well as
re-fitted into the latest D3. Given what's going on with D3 7.5 for
current platforms and Vista and W2008, the chance of them
accomplishing all of these feats anytime in this decade are, IMO, just
not worth a bet.

At this point for anyone looking for serious ODBC, I think migration
to a new DBMS would be less expensive and could be accomplished in
much less time. From what I've seen, both Caché and Reality have
exceptional relational handling as well as a clear migration path from
D3. Calling it as I see it, sorry.

T
.

Relevant Pages

  • Re: D3 ODBC Problem
    ... I must admit that I am very concerned about their failure to address Vista as this is the basis of Server 2008 and like it or not this is where the world is going. ... including FSI for *nix and the new ODBC client/server. ... accomplishing all of these feats anytime in this decade are, IMO, just ... exceptional relational handling as well as a clear migration path from ...
    (comp.databases.pick)
  • Re: Vista compatibility problems with Word 2000 mailmerge
    ... If you are starting from a new Vista installation, the thing most likely to be missing on your system is the ODBC DSNs that your Word documents expect to find. ... Unfortunately, because you cannot open a WOrd Mail Merge Main Document unless the data source is present, it is sometimes impossible to discover what the data source used to be. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Driver: MS OLE DB Provider for ODBC Drivers (for Vista 64)
    ... The reason why you are not seeing the ODBC drivers in Vista 64 is that it we do not have 64 bit drivers for ODBC. ... Vista 64 installs only with MS SQL driver. ...
    (microsoft.public.data.odbc)
  • Re: OLE DB Providers on Vista Home Premium
    ... The Vista administration tab is only for managing DNS ODBC ... connections and cannot be used for either DSN-less ... ODBC connections or for OLEDB connections (unlike ODBC, ...
    (microsoft.public.data.oledb)
  • Re: HELP- Desperate for ODBC Drivers
    ... all using ODBC to grab data from Access, Excel, and Oracle files for ... But in Vista 64, I only see a driver for SQL. ... Microsoft that will install all the needed ODBC drivers and get my data ...
    (microsoft.public.windows.vista.general)