Correction on the func table, I had missed a CVS error was looking at the wrong code. We added a fourth arg that Harbour doesnt have, so DBENTRYP_RVVL should be the right and simple fix, right?
So the main issue now is the field types -- Brian Hays Subject: [xHarbour-developers] RDD compatibility Miguel and friends: Im not sure of the state of compatibility between Harbour and xHarbour RDDs. The Harbour RDDADS code has some problems with our current cvs that Im hoping you can educate me on. In ads1.c, it changed some of the field type constants and renamed the following #defines in hbapirdd.h and usrrdd.ch xhb hb HB_FT_DATETIME HB_FT_TIME HB_FT_TIMESTAMP HB_FT_DAYTIME HB_FT_PICTURE HB_FT_IMAGE (xhb has HB_FT_TIME as no. 21) I had to change HB_FT_TIMESTAMP and HB_FT_PICTURE in ads1.c so I could build Question 1: Are we planning on syncing these changes? If so, Ill wait to pull in rddads until that happens since hacking it locally will just create problems later. If not, I need to know which hacks are safest. Question 2: in the func table, in ads1.c I had to change 2 instances of DBENTRYP_RVV with DBENTRYP_RVVL for adsDrop and adsExists. Im not sure what the L ends up doing here, especially since both projects have the same code and arg list for these funcs. Is that change appropriate, or are we going to sync usage of these flags in that table? Thanks, -- Brian Hays ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers