On 2012.02.07 07:59, Riaz Khan wrote:
> Can anyone suggest any solution,
Self contained sample.
Regards,
Mindaugas
What does this mean. What is required NOW...I have provided a self contained sample..I do not get this when chaning to 'hbsix.ch'
This means that
1) Viktor had to change HBSix.Ch to hbsix.ch to test your sample,
because the ch is lowercase, and this makes difference on various
non-win systems.
2) Your code calls MSGINFO, that is not an harbour standard function,
so the error you are reporting couldn't be tested.
A self contained sample should have only the code necessary to show
the error you are reporting, people can't stop everything to fix your
code first so then they could analyze the problem itself. There's an
excellent link in the INSTALL file with many hints about how a proper
SCS should be: http://sscce.org/
Regards,
Bacco
Hi,
Sugestions:
- Never use recno() in the index tags.
- Pack not perform changes on memo tables
For a good life in your memo tables, after pack:
- Open a table with a memo
- Copy your structure to another file.
- Rename the old table to tempname
- Rename the new table to old table name
Good luck!
Hi,
> Pls. try this for a sample..:
I compiled your example and it works without any errors.
What is the problem?
best regards,
Przemek
Hi Riaz,
> The problem is ...
> APUR.DBF:
> The APur.dbf file is encrypted with password...has NO memo field...Seek and
> Pack work fine..
>
> The BPur.Dbf file is also encrypted with password....(BUT does not get
> Encrypted ) and has a memo field....
> Results: Encrypting file with a password only is applying to files without
> memo fields..
When I was adding support for SIX3 encryption to [x]Harbour i blocked
it for tables with memos. I made it intentionally when I found few
serious bugs in SIX3 implementation when tables with memos are encrypted.
I didn't want to replicate them and make [x]Harbour RDDs bug compatible
with SIX3 because SIX3 is corrupting data in some cases.
I left them to the moment when I'll find some spare time to precisely
document SIX3 bugs and differences in new implementation.
Meanwhile I decided to block support for SIX3 encrypted tables with
memos to not have backward compatibility problems with data created
by [x]Harbour RDDs before I'll introduce workarounds for SIX3 bugs.
best regards,
Przemek