---

• Can I Create A Royalty Free Distribution?
• Is WordConverterX "Visual Studio .NET" compatible?
• How can I add WordConverterX to a VB.NET Project?
• Are there any known bugs?
• What Development Environments can I use WordConverterX in?
• Can I create a command line tool?
• Problems Occur when there are Macros in the Excel Spreadsheet
• I'm using Borland C++ Builder v5.0, why is it not showing up after importing?
• Using .NET
• Visual FoxPro, unable to register with Final Key

---

Revisions

1.662 to 1.67 (9/17/2002)

1. Concatenation of UNICODE files now supported

1.661 to 1.662 (7/17/2002)

1. Full .NET compatibility shown, and demo VB.NET source provided.

2. FileExists() check improved for better error handling

1.66 to 1.661 (5/6/2002)

1. Added ExcelGetNumberOfSheets() method to give users access to the number of sheets a give Excel file contains.

2. Special processing methods added for concatenation and massaging of converted files.  Numerous methods included for handling CSV files.

1.65 to 1.66 (3/11/2002)

1. Added SpecialProcessing() method to do special data massaging after conversions have been done.

1.64 to 1.65 (2/16/2002)

1.  Added ConvertExcelDocSheetS() to process multiple files and even subdirectories

2.  Added ConvertWordDocS() to process multiple files and even subdirectories

3.  Added GetFilesProcessedCount() and GetFileProcessed() to allow calling app to retrieve list of files processed with the ConvertWordDocS() and ConvertExcelDocSheetS() methods.

4. WordConverterEXE supplied demo source code enhanced to include new methods and properties.

5.  Added a duplicate set of methods and properties that only us the VARIANT data type, so VB Script users can be happy

1.62 to 1.64 (1/1/2002)

1.  DLL interface added to WordConverter.OCX 

1.62 to 1.63 (12/19/2001)

1.  WordConverterX can select the sheet number to convert. Formerly, only the first sheet in a  work book would be converted.  

2.  Error handling now implemented thoroughly.  New error codes:

       A) -5  = Invalid Sheet number specified

       B) -6  = Source and Target file are the same

       C) -100 = Conversion failed, ensure MS Office installed

1.61 to 1.62 (11/26/2001)

1.  WordConverterX can now be used to create a command line tool.  

2.  Sample VB program now contains command line tool source code.

1.60 to 1.61 (9/5/2001)

1.  Excel files were being converted and saved with password protection.  This was fixed so no password is required to open the file.  This error would exhibit itself when converting a TXT file to an XLS file. 

Back to Top

Can I Create A Royalty Free Distribution?

Of course.  However, you MUST purchase the released version to do this.  Shareware versions cannot be cracked, and will timeout on the end users machine, causing embarrassing nag screens to come up.

Back to Top

Is WordConverterX "Visual Studio .NET" compatible?

Yes.  In fact demo source code comes in VB6, VB.NET and Borland C++ Builder version 6.

Back to Top

Are there any known bugs?

All known bugs have been submitted and fixed.  See Revisions above for version to version details.  Also, Please submit a bug if you find one.

Back to Top

---

What Development Environments Can I use WordConverterX in ?

All 32 bit development environments that support 3rd party ActiveX/OCX components..

Back to Top

Can I create a command line tool?

Yes.  A sample VB program is shown below.  Also check out a command line product that is ready to go WordConverterExe:

The sample VB code below illustrates how to create a command line application with WCX.  The syntax is: WCX.EXE {SourceFile} /t{TargetFile}

Global Const CT_CSV = 6

Sub Main()

  If Command = "" Then

    frmDemo.Show

  Else

    Dim bResult As Long

    Dim sSourcePath As String

    Dim sTargetPath As String

    Dim lTargetPos As Integer

   

    lTargetPos = InStr(Command, "/t")

    If (lTargetPos = 0) Then

      MsgBox ("No Target File Specified")

      End

    End If

   

    sTargetPath = Right(Command, Len(Command) - lTargetPos - 1)

    If (InStr(sTargetPath, ":") = 0) Then

      sTargetPath = App.Path + "\" + sTargetPath

    End If

    sSourcePath = Left(Command, lTargetPos - 1)

    If (InStr(sSourcePath, ":") = 0) Then

      sSourcePath = App.Path + "\" + sSourcePath

    End If

   

    Dim WCX As Object

    Set WCX = CreateObject("WORDCONVERTERX.WordConverterXCtrl.1")

    WCX.vKey = 1234 ' Must enter a valid key here

    bResult = WCX.vConvertExcelDoc(sSourcePath, sTargetPath, CT_CSV) ' CT_CSV

 

    Select Case bResult

      Case -1

        Call MsgBox("Shareware Expired", vbOKOnly, "Failure")

      Case -2

        Call MsgBox("Source or Target file path is empty", vbOKOnly, "Error")

      Case -3

        Call MsgBox("Source file is invalid", vbOKOnly, "Error")

      Case -4

        Call MsgBox("Failed to Convert", vbOKOnly, "Error")

    End Select

  End If

End Sub

Problems occur when Macros are in the Excel Spreadsheet

Set the macro security to High to avoid the popup window in Office 2000.

Back to Top

I'm using Borland C++ Builder v5.0, why is it not showing up after importing?

• Download the 3 files from:  www.burble.org/aphrael/borland/borland.html
• In the downloaded utilcls.h file, do a search and replace all "FUnction" with  "Function"
  Replace the utilcls.h files in the CBuilder5\Source\VCL and CBuilder5\Include\VCL directories
• Select "Component | Import ActiveX Control..."
• Click "Install"
• Let BCB create a new package project and let it replace files.  DON'T let BCB build the new package yet.
• Run TLIBIMP {name of your VB .ocx} with the "undocumented" -Yu option (We're uncertain what -Yu officially does, but the effect is that it makes your  component(s) visible).  You will want TLIBIMP to replace the files created  when BCB installed the .OCX.
• Replace the files created when BCB installed the OCX (see the Program 8FIles\Borland\CBuilder5\Imports\ directory
• Make sure the {FINDINFILES_TLB.cpp} file is included in the package (by default it is dclusr50.cpp).  Edit
  the {package name}.cpp file and see what files are listed.  Place the following line USEUNIT("..\Imports\FindInFilesX_TLB.cpp") below USEUNIT("..\Imports\FindInFilesX_OCX.cpp")
• Now, return to the package project window and compile.

When done, install the package and your controls should appear on the chosen palette.

Do You Have Sample ASP Code

<%

Option explicit

Dim lngResult

Dim objWordConvX

Set objWordConvX = Server.CreateObject("WORDCONVERTERX.WordConverterXCtrl.1")

Response.Write typename(objWordConvX)

'objWordConvX.Key = XXXXX

'lngResult = objWordConvX.ConvertExcelDoc("C:\book1.xls", "C:\book1.html", 44)

'lngResult = objWordConvX.ConvertWordDoc("C:\word1.doc", "C:\word1.html", 8)

Set objWordConvX = Nothing

%>

Back to Top

Visual FoxPro, unable to register with Final Key

Assigning the KEY property within the code does not seem to be enough.  Copy the Final key directly into the Key Property on the ActiveX.

Back to Top