Persistent fields - ADO - Oracle database



Hi,
We have a client/server application written in Delphi 7 which uses ADO to
connect to Oracle and SQL Server databases.

A client site has been having trouble with their Oracle version being
unstable in Oracle 9.2.0.1. Oracle advised them to move to 9.2.0.7 to
attempt to resolve their problem. It's a Solaris Unix site.

However, on attempting to run our .exe, after upgrading the database, a new
bug has been introduced with Delphi. The database has a field which is
NUMBER(1) in size. With Oracle 8i (my development environment), the
persistent field was created as a TFloatField. However, an error message is
now being displayed in the Oracle 9.2.0.7 environment "Type mismatch for
field '{field name}', expecting: Float actual: Integer.

Now, looking at the field I guess I can see why it would like it to be an
Integer. This has always run fine before on Oracle 8i, 9.2.0.1 here and
9.2.0.1 at site. It also works with SQL Server. I guess I can always code
something to get around this (somehow), but I'm a bit concerned that this
initial error could be the type of the iceberg (so to speak).

Has anyone experienced this before? (i.e. differences between Oracle
versions?)
I'd be pleased if anyone could shed some light on this situation.

Kind Regards,
Mick Board


.



Relevant Pages

  • Re: Why not Access...?
    ... Next, I DID NOT SAY Oracle was considered a "best choice," only a sufficient ... It is a desktop application and the database in also on the same machine. ... I also want to know why Oracle is considered a best choice as compared to SQL Server. ... > Also, you need to answer the question regarding whether or not each client> will be using an individual database, and individual copy of a central> organization database, or making straight calls to a centralized ...
    (microsoft.public.sqlserver.server)
  • Re: Merge/Replication or Syncing with Oracle
    ... You can't directly access an Access database on the desktop from a WM 5 app, but you can sync between SQL Compact on the WM device and Access using the Access Syncronizer: ... As for the Oracle issue ... ... Where SQL Compact Edition easily does merge/replication to SQL Server using IIS ... ...
    (microsoft.public.sqlserver.ce)
  • Re: Oracle vs SQL Server as a back end for Access?
    ... post -- comparing back end database engines or replacing the front end ... say that Oracle 10g is better than SQL Server 2000 without determining ... whether or not the total cost of ownership of 10g over SQL Server ... developer than Oracle 10g, in spite of its new web interface. ...
    (comp.databases.ms-access)
  • Re: Oracle licence question
    ... And no - it does not freeze anything, the backups DO NOT affect connections ... SQL Server MVP ... freeze the database and send it to the target. ... What I really wanted is something that lists features I get in Oracle ...
    (comp.databases.oracle.server)
  • Re: What so special about PostgreSQL and other RDBMS?
    ... That's exactly the link the licence agreement for the database points to when it ... comes to what wecan expect for paying support. ... > "Oracle may provide additional releases or versions of its programs ... If the requirements are volatile I'd do a long term contract detailing what ...
    (comp.lang.php)