Moose74

Cheers for all the help and info guys!

have got a much clearer view on everything now!

Try dig into the Window server and search the file pro4.ini

It probably tells you where is PROPATH (the folder which stores the bootstraps) and PRODATA (the folder of data files, if your system uses PRO-ISAM). Or else, it tells your what database you are using and how to connect to it.

Cheers,

Yeah that gives me a datafolder, looks like it is using the ISAM.
Also from the looks of this none of it is backed up as its listed in the backup software.... hmmm


Cheers for all the help guys!

Pro-ISAM files almost always have their default extension, which is ".pro".

Aha!

Yup got a ton of these files, some of them very large which i would imagine would be database files!

You any idea what default folder would be used for database files?

Also anyone know if its possible to open these files in some other application,
(Excel, Access, SQL server or other) and check the contents?
Obviously only would attempt this with copies of the files in a safe location! lol

Cheers, Thats been a great help!

Hi Moose!

Why are you mapping a printer via net use?. Is such a printer availble thru the network? if so I would add the printer as a network one in the server and ProIV instead... just a kindda confusing to me...

Hi,

System seems only to be able to print to the LPT port.
Doesn't use windows system printers as far as i can tell.
(think it was originally written in an old dos version of ProIV)

Actually can map the printer from within ProIV to whatever printers are on the client PC but we don't get the correct output - &&&&&& symbols instead of lines that are supposed to (and do on somemachines) appear.

Whats the "in-house" system name, that could provide a fast track to solving your problems ?

Hi,

System is called "WMCOM" , i've got a .piv file thats run on the client machines to gain access to the system. I'm assuming this is some sort of scripting file?

A short cut calls the Proiv.exe file and passes the parameters
"wmcom.piv -P LOG LOG HDATA"