#28737 - 2002-09-09 10:46 PM
INI output
|
Anonymous
Anonymous
Unregistered
|
I see a lot of scripts that spit data out in the classic Windows INI format. Why is this done? Do you read the data in a special program or database? What're the pros of spitting data out in INI format vs something like one big tab delimited file?
I'm doing a hardware/software inventory pretty soon and I'm wondering how I should output the data so that I can read it. I was going to do 1 tab delimited file per workstation and then concactinate them all into one file and suck it into Access. But that makes for one hell of a long WRITELINE line. The INI output seems more attractive, but I don't know how I'd get it into a database.
Thanks.
|
|
Top
|
|
|
|
#28740 - 2002-09-10 05:30 PM
Re: INI output
|
Anonymous
Anonymous
Unregistered
|
Pardon the ignorance, but what do you use to read and write to INI files? Are there any programs that do that? I don't mean text editors, but database progs for INI files.
|
|
Top
|
|
|
|
#28742 - 2002-09-10 06:31 PM
Re: INI output
|
Anonymous
Anonymous
Unregistered
|
I guess I'm just not clear on why you would put data in an INI file if there's no progs to display the data other than a text editor.
I was thinking that there might be a program to read a bunch of INI files with the same formatting and show you the data all neat like.
My only experience with data in text files would be with tab or comman delimited files that can be queried with Access or Excel or MSQuery, etc. I thought you could do that INI files.
|
|
Top
|
|
|
|
#28745 - 2002-09-10 06:49 PM
Re: INI output
|
Anonymous
Anonymous
Unregistered
|
Ok, Les, Jens, I got it. I can use a script to write my software/hardware inventory info to an INI file for each PC. Then I use another script to put all of the info in each INI file into a tab/comman delimited file which I then can query with Access or somewhat.
Now to figure out how to read INI files and put the data in a CSV or somesuch.
Thanks!
|
|
Top
|
|
|
|
#28748 - 2002-09-10 07:37 PM
Re: INI output
|
Anonymous
Anonymous
Unregistered
|
Well, what I've been doing is writing a text file with one line per PC (per PC that runs the script). The data is tab delimited with the workstation name being the first bit of data.
When the script runs it checks to see if the file (which is named after the workstation) exists. If it does, it skips the script.
When all the PCs are inventoried, I copy all the files into one big text file and import that file into Access.
I'd write the data to one text file, but I don't know how to check if there's already an entry in the text file for the PC that's running the script.
So I thought as long as I was writing one file per PC would there be some advantage to doing it in INI format. Then I started this thread.
I'm really not very good at this scripting stuff.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 2220 anonymous users online.
|
|
|