Subject | Re: [Firebird-Architect] Enumerated Types |
---|---|
Author | Doug Chamberlin |
Post date | 2003-07-15T10:47:26Z |
At 7/15/2003 06:01 AM (Tuesday), rogervellacott wrote:
it is too specific to a certain type of client.
Most solutions to this problem are achieved by adding a layer to your
applications, a middle tier, which centralizes the translation you need. I
see you are stuck in 2-tier, "client-server think". Break out of that model
into multi-tier!
Borland has done a great disservice to application designers by not
providing more guidance in how to accomplish multi-tier (without additional
licensing costs). After all, they are ones who firmly fixated everyone
early on to the direct access model using TDatasets and data bound
controls. Try the OODesign newsgroup at newsgroups.borland.com for more help.
>I keep coming up against the problem of interpreting DelphiA practical suggestion but hardly suitable for the database server because
>enumerated types into database field values and back again...
it is too specific to a certain type of client.
Most solutions to this problem are achieved by adding a layer to your
applications, a middle tier, which centralizes the translation you need. I
see you are stuck in 2-tier, "client-server think". Break out of that model
into multi-tier!
Borland has done a great disservice to application designers by not
providing more guidance in how to accomplish multi-tier (without additional
licensing costs). After all, they are ones who firmly fixated everyone
early on to the direct access model using TDatasets and data bound
controls. Try the OODesign newsgroup at newsgroups.borland.com for more help.