Very Computer

by **BSC** » Fri, 10 Mar 2000 04:00:00

All the postings on this subject are no longer available for me to look at.
We can enter data via Access into a DB2 table with Time field but when we
try to retrieve them Access marks the records as deleted. What is the fix?
workaround? etc?

by GT » Fri, 10 Mar 2000 04:00:00

I used patches = 1036 on the ODBC data source, which is three
incompatabilities fixed. Can't remember them all.

>All the postings on this subject are no longer available for me to look at.
>We can enter data via Access into a DB2 table with Time field but when we
>try to retrieve them Access marks the records as deleted. What is the fix?
>workaround? etc?

--
Gary Talda

by **Phil Castl** » Sat, 11 Mar 2000 04:00:00

I'm not sure if it's relevant to your situation, but some years ago we had a
similar-sounding problem with Access. All our rows (on some tables) were
marked as #Deleted# when we tried to display them. It turned out that this
happened for every table which had a numeric primary key.
We never found a circumvention and Microsoft didn't seem particularly
interested in it. It caused a major delay in our project as we had to
redesign all our tables to have character primary keys.

Phil Castle

> All the postings on this subject are no longer available for me to look
at.
> We can enter data via Access into a DB2 table with Time field but when we
> try to retrieve them Access marks the records as deleted. What is the fix?
> workaround? etc?

by **Ala** » Sat, 11 Mar 2000 04:00:00

>All the postings on this subject are no longer available for me to look at.
>We can enter data via Access into a DB2 table with Time field but when we
>try to retrieve them Access marks the records as deleted. What is the fix?
>workaround? etc?

Is the Date, Time, or Timestamp column part of the primary key or part
of the indexes? I have seen #deleted# in this situation (over a year
ago) and it was not a IBM problem but a MS problem. I can't remember
how to get around the problem but I think we put a view on the table
and then used it.

Alan

by **BSC** » Sat, 11 Mar 2000 04:00:00

DB2 gave me a fix where you put a entry patch2=24 under the section for your
database DSN. There are other entries for other problems. Also, this problem
only happens when you have a time field in the key.

> I'm not sure if it's relevant to your situation, but some years ago we had
a
> similar-sounding problem with Access. All our rows (on some tables) were
> marked as #Deleted# when we tried to display them. It turned out that this
> happened for every table which had a numeric primary key.
> We never found a circumvention and Microsoft didn't seem particularly
> interested in it. It caused a major delay in our project as we had to
> redesign all our tables to have character primary keys.

> Phil Castle

> > All the postings on this subject are no longer available for me to look
> at.
> > We can enter data via Access into a DB2 table with Time field but when
we
> > try to retrieve them Access marks the records as deleted. What is the
fix?
> > workaround? etc?

by **d_taggar** » Sat, 11 Mar 2000 04:00:00

You probably have a decimal field in your primary key. MS Access does not
understand decimal data type, they convert it to FLOAT (I believe), a duplicate
can be produced due to rounding, that's why you see #delete#. If you only need
read access to the table then open the result set as a SNAPSHOT (read-only),
that should get rid of the #delete#

There is a trick to tell Access to use a different unique index (if you do not
have a PK defined on the table) that does not involve decimal data type. If
you need it I can try to look it up.

> All the postings on this subject are no longer available for me to look at.
> We can enter data via Access into a DB2 table with Time field but when we
> try to retrieve them Access marks the records as deleted. What is the fix?
> workaround? etc?

Very Computer

Yes, MS Access having problems with DB2 Time datatype #delete

Yes, MS Access having problems with DB2 Time datatype #delete

Yes, MS Access having problems with DB2 Time datatype #delete

Yes, MS Access having problems with DB2 Time datatype #delete

Yes, MS Access having problems with DB2 Time datatype #delete

Yes, MS Access having problems with DB2 Time datatype #delete

Yes, MS Access having problems with DB2 Time datatype #delete