Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

codepage

Status
Not open for further replies.

nguntay

Programmer
Oct 5, 2004
20
TR
Why does not Codepage 857 or codepage 1254 work if you write directly onto screen (@ say/get), while it is ok on the forms.?
 
Since the @ say/get is "old type" of coding you may want to ask in forum182.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
Dear Mike,
1- If you noticed , I am talking about the "codepage" which is not an item of old DOS-FOX. Therefore it's place may not be the "old type".
2- Though, @ say/get is an old type, it still is available in vfp9 and thousands lines of @ say/get code is working in my foxpro applications under vfp9. Therefore , I am trying to find out the reason of why it is not functioning correctly.
3- I have searched the whole form for this subject if an answer could be awailable. Anyway, If you have one, I will appreciate for it.
 
nguntay

1- If you noticed , I am talking about the "codepage" which is not an item of old DOS-FOX. Therefore it's place may not be the "old type".

You could have at least posted the question in the forum182 and see what they know about the situation. Codepage was being used in FoxPro 2.6. I meant no disrespect in the style of coding you are using, I just meant that you may have had a better chance to resolve your issue in a forum that uses that style, and many of the experts there are "crossovers" that use both FPW and VFP, where the reverse might not be as true.



Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
Mike
at start the special characters like "iü??ç??Ü??ÇÖ" (special Turkish Characters) are perfectly echoed to the screen by say get comments ,
But after the old program (foxpro 2.5 coding) continues to execution , the echoed characters are replaced by entirly different ones. (ON print everythings OK.)
I can shows this to you only by screen capture, but don't know how to show it here .

Possibly, one of the commands issued later , causes this to happen but which one? What about "set disp to vga25" command ?


regards
 

nguntay,

So, are you saying that your Visual FoxPro works correctly, but when you run your FoxPro 2.5 application then go back to Visual, the Visual app is no longer producing the correct display?

If so, I suggest you try taking commands out of the 2.5 app until it starts working again. That way, you'll know which command caused the problem.

I doubt if it is SET DISPLAY TO VGA25, as that would only affect the DOS display.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)
 
Yes and no, Mike,
Visual FoxPro works correctly, yes.
But Visual FoxPro( -NOT foxpro 2.5-) executes the "foxpro 2.5 code" uncorrectly. ( I am trying to run the old 2.5 code under vfp8 without any change. (over a 100,000 lines of code, and most of the user interface done by @ say/gets.) Somehow I am quite successfull with it, except the page coding.
 
nguntay,

have you tried to put the codepage in the config.fpw?

Rob.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top