Preproc Issue

[MauditOstie]

Hi Peggers!
I'm having a hard time about preproc issu.

i have a Program A.p wich does a buffer-compare.
therefore i have a list of fields store in a variable.
i need to do something like this:

PROG A.p
Do i = 1 to num-entries(List):
{proga.i &TableName = testtable
&FieldName = ENTRY(i,List)}
end.

Proga.i
Create Newtable
assign NewTable.field = STRING({&FieldName})
NewTable.table = STRING({&TableName})
NewTable.Value = ??????

?????? -> I got no idea how to use the content of both variable to create the testtable.Field assignation...
i've tried a cpl such as '{&TableName}'.{&FieldName} but it gives me an error saying "Could not understant after "NewTable.Value = testable"'
witch means i got the "table" usage right but can't get the field to work...
Anyone got an idea?

Thanks

Rob

 

[jongpau]

I don't think you can use a variable as an include parameter in that way. What Progress version are you using?

 

[MauditOstie]

Hi jongpau, well i think you are right, there is no way to do it!
9.1d on AIX, RS6000, CHUI.

I was able to figure a way out, without using Preproc (cause i got kinda mad last night )

I've switch things using Handle and Buffers and was able to make everything worked fine (even found out while reading the net that Buffer-Compare has a bugs and has problem with Decimals!).

thanks for taking time to answer! If ne1 wants to know how to do it let me know! I'm the codesharing type of guys

 

[jongpau]

Hi Rob,

That was why I asked what Progress version you are using --> my next suggestion would have been to use dynamic buffers

Can you please tell some more about the problems you have found that may exist with buffer-compare and decimals? What are these problems and are these related to a specific Progress version?

 

[MauditOstie]

Well from what i could see, progress seem to be having problems with the decimals! It seems to be linked to the number of decimals!

Exemple:
if i have 1.77889888 store in progress and the dictionnary is set to a format:
9.999
Therefore each time i would update the table containing that field, if i don't even touch the field, the "Old" value would be 1.77889888 and the new one would be 1.779??? Some kind of problem like that!

Ever heard of that? I would need to test it more deeply but i think that was the problem!