>>>>We've run into some problems locating exactly what data manager was used with, apparently, with files with a tlb extension. The following code snippet is some that's apparently used to access these files

>>>>if SETUP->NFEET = 0 // use metric conv.
>>>>  nstit := _sper3
>>>>  nsper := setup->nsper
>>>>endif
>>>>fwindow( 6, 3, 15, 43, "GR+/RD,N/W,N", .t., "Executing Commands, "DOUBLE")

>>>>Don't mean to be short on the sample, but if I were asked to describe the language, I'd say it looks like a cross between xBase, Pascal (note the assignment statements), and C (note the comments).
>>>>
>>>>My gut reaction is Clipper, but I've never laid eyes on line one of Clipper code, so I can't say for certain.
>>>>
>>>>tia,
>>>
>>>I don't know, but I found quite a few on my computer by doing a search on *.TLB. maybe if you did the same, some of the file names might give you a better idea. Many of these were in my WinSys directory.
>>
>
> The .TLB files in the Windows directories are probably Type Library files. I'm not sure why Clipper would need them. It's possible they just happen to use the same file extension.
>
> The above code >could< be Clipper code, but I don't recognized the fwindow command. It could be some sort of add in library.

Hi Paul

Thanks for the feedback.

They're not (the TLB files) type libraries. Using the "hacker's best friend" (the HexEdit.app) they seem to be the table structure definitions. A second file exists with same primary name, but with the extension MBM. This may contain the data. I haven't been able to determine for certain if this is the case, however.

Thanks again,