On Mon, 8 Nov 2010, Enrico Maria Giordano wrote:
> Let's rethink about this: why we should introduce this new setting? Currently
> a DBF with memo fields is not encrypted at all. If one doesn't want to
> encrypt a DBF just don't use DBI_PASSWORD, what's the problem? But if one
> wants encrypted it, well, currently he can't if the DBF has memo fields.
> Removing this limitation we leave more freedom to developers.
According to the links you posted, encryption for DBF
with MEMO fields is NOT backwards compatible.
I agree it (encryption for DBF with MEMO fields)
should be supported, but as an extension.
Any developer sharing files with old (Clipper)
executables could try to open these files with
xHarbour code. It's required any kind of warning
to avoid data corruption. IMHO, an "optional flag"
would be useful.
Atte.
Vic
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
