>>>>>>>Till now i've been transferring my reports in word & excel and was facing version problems..(Errors in Office 95/97)
>>>>>>>
>>>>>>>After posting question for this, i realized HTML option is also avl..
>>>>>>>
>>>>>>>I guess Vfp 6.0 is giving option of transferring reports in HTML... if yes, how sucessful it is ?? Are the reports transferring 100% perfectly...
>>>>>>>
>>>>>>>I'm still using version 5.0a, What will be the best thing to do ?? To shift to 6.0 or create my own class to transfer in HTML ??
>>>>>>>
>>>>>>>Whether I shud choose HTML or Word/Excel ??
>>>>>>>
>>>>>>>
>>>>>>>Can somebody pls help me on this...
>>>>>>>
>>>>>>>TIA
>>>>>>
>>>>>>THe way that VFP converts reports to HTML is with GenHTML. This program internally uses REPORT FORM TO ASCII to get the report to a file. The file is then parsed and converted to basic HTML.
>>>>>>
>>>>>>This is fine, except the TO ASCII clause of REPORT FORM is a nightmare.It does NOT preserve field placement and some of your fields might be cut off in the output. What's worse, if you tweak your report just right so that its output works with TO ASCII, changing to a different printer might break it (even though you are not printing the report, VFP uses the current printer driver to render the text for TO ASCII). IMHO, the only practical way to get an HTML document from VFP data is to generate the HTML yourself.
>>>>>>
>>>>>>As for other document alternatives, you might want to look into PDF. Once you have the PDF writer software, converting a VFP report to pdf is as simple as printing it to the Acrobat "virtual printer".
>>>>>
>>>>>Thanks for the detailed reply abt. html transfer.. I guess its better to make HTML Code myself...
>>>>>
>>>>>I wanted to know your advice, Whether I shud convert Reports in HTML or better to create in word/excel(where have to write too much code for each version)..
>>>>>
>>>>
>>>>Why don't you just always write for the oldest version?
>>>
>>>Which version ?? Do You mean the older version of Microsoft office ???
>>
>>Yes. If you write your documents in office 2.0 format or something, than all versions can read it.
>
>I'm using office 95 and that i chkd is Office version 7.0 (right ??)...
>
>I don't have this version, how i can know commands used in this and test it...
>
>pls help..

Wait a minute, I misunderstood your predicament. I ws tihnking htat you needed documents that can be read by any version, but what you need is code that will automate any version.

Well, part of your answer could be sticking with WordBasic commands instead of VBA. Even with Office '97 (and probably Office 2000, but I haven't checked) you can instanciate a Word.Basic object instead of a Word.Application object. If you only use the Word.basic object, your code will be compatible across version of word. You just need to make sure you have a copy of the old WrdBasic.hlp file to help you figure out what you are doing, or an old version of word that you can record macros with.