jd asked: > Here's how I figured I'd have to convert from MS Access types to SAPDB types: >number(long) -> integer, > date/time -> date, text -> varchar, memo -> long(ascii), currency -> float. Do you >see any potential problems with > this? I'm particularly nervous about the data/time fields and memo field conversions.
If we are talking about SQLMODE Oracle, the datatype date will be able to include date and time together. if we are talking about the SQLMODE internal (default), date just includes the date, no single bit for time, the datatype time includes just the time, no single bit for date. The only datatype to include both is timestamp. And as others mentioned before: the transaction-handling is very inportant. If one task is inserting data, it has locks on that data until commit or (implicit if session stops without explicit commit/rollback) rollback. Other tasks selecting will come along the data and find a row locked (by the inserter). With default-isolation-level 1 they are not allowed to see data neither committed nor rollbacked, but just somewhere in the middle of a transaction. The selector therefore waits until the lock is closed (by commit/rollback of the inserter) and there was (by that transaction) a decision made if the data will stay or will be deleted by rollback. Therefore the selecting task seems to be locked. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
