|
Home > Archive > Unix questions > August 2006 > Unix and Windos
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Mohsen 2006-08-21, 1:23 am |
| Hello everybody,
I am running my program in Unix and after every run, I have to transfer
my results to Windows to design a graph of my results in Excel.
I would like to know if there is any possibility to make a link between
Unix and Windows to be able to run Excel every time that Unix finishes
its job.
Thanks,
Mohsem
| |
|
| You can use CD (Connect direct) to run remote jobs. It's paid software.
Alternatively, you can save the results on a samba share. Have a VB
program looping for this particular file name which you save and
process it.
Ram.
Mohsen wrote:
> Hello everybody,
>
> I am running my program in Unix and after every run, I have to transfer
> my results to Windows to design a graph of my results in Excel.
> I would like to know if there is any possibility to make a link between
> Unix and Windows to be able to run Excel every time that Unix finishes
> its job.
>
> Thanks,
> Mohsem
| |
| Lew Pitcher 2006-08-24, 1:38 pm |
|
Mohsen wrote:
> Hello everybody,
>
> I am running my program in Unix and after every run, I have to transfer
> my results to Windows to design a graph of my results in Excel.
> I would like to know if there is any possibility to make a link between
> Unix and Windows to be able to run Excel every time that Unix finishes
> its job.
Hmmm. I don't know of any easy way to trigger the start of a Windows
process from Unix. But, if you can manually start Excel, you have a
number of options as to "making the data available" from Unix
You can
1) export the filesystem using NFS, and mount the filesystem to Windows
with a 3rd party NFS client. That way, the results file looks to be a
file on a local drive to the Windows system, and can be pulled into
Excel that way
2) export the filesystem using SMB, and mount the filesystem to Windows
with the "Microsoft Networks for Windows" client. That way, the results
file looks to be a file on a local drive to the Windows system, and can
be pulled into Excel that way
3) record the data to a local (Unix) RDBMS, and use an ODBC connector
on Windows to access the data. Excel can read through the ODBC
connector the data as recorded in the database
4) (Exotic) Have the unix process email the results file to the WIndows
user. User saves file and runs excel
5) (manual) Windows user FTPs file from Unix, procedes as above
6) (overly complex) Store resultset in a webpage, Windows user accesses
page, pulls resultset down, runs it into Excel. IIRC, Excel can strip
tables out of webpages for you, so this might not be too manual a
process
HTH
--
Lew Pitcher
|
|
|
|
|