Here are some extended EDB 2 components with the following additons:

- Property EmptyStringsAsNull: Boolean default True.
This will clear empty strings to NULL on posting a record. So no empty strings should be in the table after a post.

- Handling of a new special DB Table/View/Procedure attribute CURRENCY=Field1;Field2;... which controls, if a Float/BCD Field should be handled as a currency field. If this attribute is found on opening the Table, it will automaticly set the Field.Currency property to True. The new property AutoCurrencyFromAttributes: Boolean default True, will controll if this should be done automaticly. There is also a new CurrencyFieldNames property in which the fields can manually be set at design time. In this case the CURRENCY attribute is not used.

Sample table create SQL:
CREATE TABLE "Payment"
(
"ID" INTEGER NOT NULL,
"Price" DECIMAL(19,4) DEFAULT 0.0 NOT NULL,
"MaxOrderSum" DECIMAL(19,4) DEFAULT 0.0,
"Discount" FLOAT DEFAULT 0.0 NOT NULL,
CONSTRAINT "PrimaryKey" UNIQUE ("ID")
)
ATTRIBUTES 'CURRENCY=Price;MaxOrderSum'

- All Active and Connected properties gets not storerd anymore in the DFM. So if you still have a table open at design time, the Active = True property will not be stored and must be manually be activated at runtime.


Usage:
If you want the property editor for the new CurrencyFieldNames or if you want this new components at runtime anyway, then you can install the DPK into the IDE. Actually only the XE4 package is included, but it would not be a big deal to make it working in other IDE versions.

As an alternative you DONT need to install anything and just inlcude the RFEDBComps unit after the EDBComps unit in the Uses list. This will make all your TEDBxxx comps into TRFEDBxxx components at runtime and you get all the functionality without to install anything.

Hope anyone will find this additions helpfull.

Regards
Rolf

Rolf.

<< Here are some extended EDB 2 components with the following additons: >>

Nice, thank you very much.

Tim Young
Elevate Software
www.elevatesoft.com

Rolf


Currency fields is an interesting one. I'll have to compare how you've done the emptystring = null bit and see if its any better than mine. I decided to just go with it because I personally will never want to post empty strings. One other thing I did was to trim fields since I, again personally, don't want trailing or leading spaces. If you want to have a loo at my code its in this NG.

Roy Lambert

WARNING

The TRFEDBScript component interface is/was wrong in the first Upload! It was a copy/paste isue. I didn't use that component myself yet, so I didn't notice its wrong proptery visibility.

Also there are no CURRENCY Attributes uses for this component. So if you want use this feature, you must set the CurrencyFieldNames property to get currency fields. And of course it will only work, if the script returns a cursor.

The interface should correctly look like this:

 TRFEDBScript = class(TEDBScript)
 private
   FCurrencyFieldNames: String;
   FEmptyStringsAsNull: Boolean;
 protected
   procedure InternalOpen; override;
   procedure InternalPost; override;
 public
   constructor Create(AOwner: TComponent); override;
 published
   property Active stored False;
   property CurrencyFieldNames: String read FCurrencyFieldNames write FCurrencyFieldNames;
   property EmptyStringsAsNull: Boolean read FEmptyStringsAsNull write FEmptyStringsAsNull default True;
 end;

Regards
Rolf

New Verison with the Interceptor class included. This unit was missing in the old ZIP file.

The interceptor class unit RFEDBCompsInterceptor.pas can be used, if you don't want install the new TRFxxx comps in the IDE or you don't want replace them in all your existing applications. So you have just to add this Unit after the EDBComps in the uses list and all is done. So is no need to change any existing DFM's and just let the TEDBxxx untouched in there. By recompiling your application your forms will uses the new TRFEDBxxx comps instead the old TEDBxxx comps as of the intercepted classes in this new unit.

Regrads
Rolf

Hi Rolf,
Like playing on the 'Bleeding Edge'
Will give them a try under DTokyo 10.2.3.

Regards,
Ian

Hi Rolf,
Said I'd have a play.
I am using D10.2.3, EDB v 2.28 Build 1.
Issue with RFEDBQuery - If I put a RFEDBQuery & a EDBQuery component on a form that has the Engine, Session & Database set up.  Set the Session, DatabaseName & SQL for each of the Querys.
In desigb time, if I now Set Active true on EDBQuery, no problem.
If I then do it with RFEDBQuery, I get a "Database name is missing." error.  
This makes testing in Design time a little difficult.
If I hook them to a table and build/run the app, Both work fine.

Is this error occurrence by design?  Have I missed some action/setting?

Regards,
Ian

"If I hook them to a table and build/run the app, Both work fine."

Should have said..

"If I hook them to a datasource and grid and build/run the app, Both work fine."

Ian

FWIW I prefer NULLs to empty strings.