Re: wk1 files, between a rock and a hard spot

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Marty,

Well, I've found the file format documentation here:

http://www.schnarff.com/file-formats/index.html#lotus

The wk1 extension corresponds to Lotus 1-2-3 version 2.0, so you will
have to keep that in mind while going through this.

If you decide not to parse apart the file, then you probably should look
for a third-party solution to do this. I did a google search for "wk1 file
parser" and came up with a few hits.

You ^might^ be able to get away with using the Jet 4.0 driver for OleDb
(and using the classes in the System.Data.OleDb namespace) to access the
data. The following is an example from Knowledge Base article 326548:

cnn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\Lotus123File.wk3;" & _
"Extended Properties=Lotus WK3;"

I assume you would substitute WK3 with WK1 where you see it.

Or, if there is an ODBC driver or other OLEDB driver that you can find
that uses this, then you could use that, and then export your data into a
format that is easier to consume.

--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx


"Marty" <mcoonrod@xxxxxxxxx> wrote in message
news:1e7a9c03-1dd0-436a-98a5-a034fa981ee6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
By the subject you may be able to tell that I am not pleased...
Here is my situation: We have an old but very useable program that
exports information out into a wk1 file.
I had a program that I had developed a couple years ago that would
open these files through Excel. This allowed me to grab specific
information that would then in turn be used in some AutoCAD drawings.
Well my nice shiny new computer with it's nice shiny new Office suite
just killed it! Excel does not support this format any more (something
to do with security issues so I can't blame them.)
So outside of going back to my old system and using that I decided I
would give it go to extract the data directly from the wk1 file
myself. Easier said than done, I am not finding anything on how I can
go about doing this. I am not a computer science engineer so my brain
is limited in the information department.
I would be pleased if anyone would be willing to share information on
this file format and maybe any past experience working with it.

Thanks,
Marty

PS. Yes I am looking into replacing the old program but that will take
time also. I need a solution in the interim.


.



Relevant Pages

  • wk1 files, between a rock and a hard spot
    ... exports information out into a wk1 file. ... Well my nice shiny new computer with it's nice shiny new Office suite ... I am not a computer science engineer so my brain ... this file format and maybe any past experience working with it. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Converting files
    ... I can't help with info about the addressbook. ... The display problem might be a video driver problem. ... Update to see if it would like to offer you a new driver for your monitor. ... offer to convert files in Word 97 is that the fundamental file format ...
    (microsoft.public.word.newusers)
  • Re: Suggestions for a consumer-level printer that will scan to USB without a PC connection?
    ... Scans are a file format (usually jpegs) but most use a TWAIN of similar driver that involves the computer memory for temporary storage, and then it can be written to disk via the TWAIN or other intelligent software. ...
    (comp.periphs.printers)
  • Re: Fujitsu and Relativity
    ... Or exist another driver of ODBC for Fujitsu Cobol indexed files? ... It may or not depending on the file format you are using. ... Best advise for that is to use the btrieve option instead, ...
    (comp.lang.cobol)
  • Re: AutoCorrectName Problems
    ... Changing to the Access 2002 file format will not make any difference. ... and download the updates for Office XP. ... This really sounds like a problem with the printer driver. ... Access uses the driver metrics to calculate the layout of the report, so it sounds like the driver is providing faulty metrics. ...
    (microsoft.public.access.reports)