HMGforum.com

Merhaba Foued

fouednoomen wrote:Can i display the first column in bold character and the second on in standard character.

As far as I know, no

In GRID and BROWSE, font properties are for whole control, no individual column;

so we haven't a possibility to change font properties ( size, bold, italic, etc ) in column basis.

Maassalam.

Salam alaykom

Many thanks for your prompt replay
In chaa Allah in the future we find solution

My friend I take this opportunity to ask you How can i activate cell navigation in browse like grid ?

Thanks in advance

Foued

I'm so sorry i could not put a new topic ,i don't know why ???

My problem is the flowing :

I have tow Applications the first one build in clipper 5.3b the second one in HMG , they use the same DBF file "ARTICLE"

when i generate index with hmg the HMG application run ok but when i run the first one build in clipper ,i have this message :Error _DBCCDX/1054 Error data type :XYCODE


many thanks
Foued

Aleina ve aleykom salam ya ahi

My friend I take this opportunity to ask you How can i activate cell navigation in browse like grid ?

Sadly, cell navigation is GRID only property; the BROWSE control doesn't support such thing

I have tow Applications the first one build in clipper 5.3b the second one in HMG , they use the same DBF file "ARTICLE"

when i generate index with hmg the HMG application run ok but when i run the first one build in clipper ,i have this message :Error _DBCCDX/1054 Error data type :XYCODE

Clipper 5.3 Error messages wrote: DBFCDX/1054 The type or length of the key doesn't match what's stored
on disk

Explanation: this error code indicates:

1. a key expression has changed since the index was created. For
example, if you had an index on LAST and changed the width of the
field from 20 bytes to 25 bytes, and then tried to use the old index,
you would get this error.

2. an index was created on an expression which has a variable length
(e.g., TRIM(last)). The key expression must always return a fixed
length.

Action: Use PADR() to ensure that the key expression is always the
same length.

In other hand, TAG keyword indicate a CDX type indexing; may be an incompatibility between Clipper and Harbour implementing this type indexes.

If possible, you may try indexing without TAG clause.

Bad news is: Harbour compiled applications can successfully open and use database and index files built by Clipper compiled programs; but the inverse isn't correct: Clipper compiled applications may or may not successfully open and use database and index files built by Harbour compiled programs

This is because Harbour have too many extensions and expansions regarding Clipper; so Clipper compiled program may doesn't recognize these extra features.

My suggestion is convert your Clipper applications as soon as possible to Harbour

Happy HMG'ing

Salam Alaykom

Many thanks for your prompt replay

I think so ,I must convert the rest of my application in Harbour


Regards

Foued