ERROR 5300

[patili]

Hi
i have one error when i want to print with Fivewin

"Clipper Internal Error"
DIBREAD(0)
Unrecovreable error 5300: not enough memory

I don't see the 5300 error in clipper doc.
Any idea?
I think it is a problem of configuration, but what?

Fw 2.2 Clip 5.3 MS link Celeron 2.8 Ghz 500Mo Ram

Thanks

[Detlef Hoefner]

Bonjour Patili,

unless i don't see your print code, i suppose you're trying to print a bitmap which is too big.

May be you could think about switching to (x)Harbour which doesn't know such errors.
I did it some month ago. It was very easy, i have no more memory errors and i did never regrett.

Regards,
Detlef

[Antonio Linares]

Patili,

Clipper does not support files larger than 64 Ks.

FWH + [x]Harbour support them

[patili]

It just send me an error when i preview a print.
But it is working very good on an other station of my network, so i think it is jjust a configuration problem.
What should i take in my autoexec.bat or config.sys ?
I use the free MS Link , will it work with Harbour?

[Detlef Hoefner]

Patili,

you will not need MS Link for (x)Harbour.
You just download the binaries for (x)Harbour and the complete Borland or MicroSoft compiler package for free.

Regards,
Detlef

[patili]

I'm coming back with my error.
My application work very well on one PC of my network, and is generating this 5300 error on the 3 others when printing a simple page without bitmaps.
How can i know the use of the memory on this 4 computers? Because it seems there is a difference.
FWH will support all my FWClipper code, and don't generate this error?
Thanks
Patrick

[Detlef Hoefner]

... FWH will support all my FWClipper code, and don't generate this error?
Thanks
Patrick

Yes, it will.

Regards,
Detlef

[patili]

And i use Hypersix driver Index *.nsx which is very fast.
What append from my indexes with FWH?

[Detlef Hoefner]

And i use Hypersix driver Index *.nsx which is very fast.
What append from my indexes with FWH?

I don't have any experience about Hypersix.
But i used comix in 16bit times which was much faster and more compact as dbfntx driver.

When changing to 32 bit i had to switch to dbfcdx.
All users in our network stated a much higher performance than before.

I really do recommend changing to xHarbour.
A lot of limitations and errors did vanish after i migrated my apps.

I thoght that i was the last mohican in the FiveWin for CA-Clipper forum who dared to jump into the 32 bit cold water
But now it seems to be up to you.

Regards,
Detlef

[patili]

AIE, i am the last!!!

if i jump to FWH this forum will DIED
I am sorry for that, but i think i will follow your example...

[James Bott]

Patili,

There will be lots of people willing to help you convert to 32bit.

You won't regret it.

Regards,
James

[patili]

Thanks everybody, in this time i have not very much time for "Clippering" (i am building my new veterinay clinic and have a lot of problems with it).
I say "Clippering" because i am and old .not. "mohican" .but. "brontosaure"
from the Clipper area. In my app, i use many of the Hypersix function:
eg: sx_setscope(), sx_keysincluded() .... and compound indexes.
Will it be easy to translate this in 32 bist

[James Bott]

Patili,

Both the CDX and NTX RDDs support scopes and compound indexes. I'm not sure what sx_keysincluded() does, so I don't know about that one.

You could probably write functions with the same names as the Hypersix functions and use the new functions to translate to the new RDD.

Example:

function sx_setscope(...)
return ordSetScope(...)

This way you wouldn't have to change all the Hypersix function calls in your entire program.

James

[patili]

Very good idea
Thnks.

[patili]

Hi everybody
i have found why my print didn't work and generate this error:
it is because the bmp file of the oprn:saybitmap( .bpm) was not on the station but on the serveur (set default to \\serveur\)
I just copy it on the local drive c:
and oprn:saybitmap( "c:\ .bpm")
and everything work well and i didn't have thie horrible error 5300

Now i will go slowly to harbour