MattX

INI Files

8 posts in this topic

I'm knocking up a script which will detect if a user is logged on and if so send an E-mail to the helpdesk.

I have a list of users in an ini file - example:

[USERS]
USER01=tuser
USER02=tuser2    
USER03=tuser3

When using iniread, will this place all them into memory as I want to state something like If @UserName  =  any of the names in the ini file do something..

Or do I need to read them in using a different method ?

 

Share this post


Link to post
Share on other sites



simply this.

@UserName=IniRead("Yourinifile.ini","USERS","USER01","")

Saludos

1 person likes this

Share this post


Link to post
Share on other sites

Danyfirex that won't work, you can't assign anything to a macro.

You can use IniReadSection to get all of the usernames in the INI file in that section and loop through them to look for the @Username.

Global $aUsers = IniReadSection("myinifile.ini", "Users")
For $Loop = 1 To $aUsers[0][0]
    If @UserName = $aUsers[$Loop][1] Then
        ;do something here
    EndIf
Next

 

1 person likes this

If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.
Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag Gude
How to ask questions the smart way!

I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from.

Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays.  -  ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script.  -  Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label.  -  _FileGetProperty - Retrieve the properties of a file  -  SciTE Toolbar - A toolbar demo for use with the SciTE editor  -  GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI.  -   Latin Square password generator

Share this post


Link to post
Share on other sites

#4 ·  Posted (edited)

thanks @BrewManNH Maybe I didn't understand the question :yawn: I'm still asleep. :sweating: :lol:

Edit: I meant compare. not assign

Saludos

Edited by Danyfirex
EDIT

Share this post


Link to post
Share on other sites

That works if the listed @UserName is USER01, what do I need to do to get it it to pick up if the UserName is say user02, user03, user04 etc.

I could repeat the

If @UserName = IniRead(@ScriptDir & "\users.ini", "USERS","USER01", "") Then

 

With a load of ElseIfs but is there a easier way to read in every line in the INI file ?

Share this post


Link to post
Share on other sites

Not fully sure why an ini file for user name, or what side of the ini file has the actual user name your searching for based on the example.  So I am assuming the key has the user name and the value is a return value you need with INIRead().

 

$aUsers = IniReadSection(@ScriptDir & "\Users.ini", "USERS")
For $i = 1 to $aUsers[0][0]
If StringInStr(@UserName, $aUsers[$i][0]) Then
$sResult = IniRead(@ScriptDir & "\Users.ini", "USERS", $aUsers[$i][0], "")
MsgBox(0, "", $sResult)
EndIf
Next

 

 

Share this post


Link to post
Share on other sites

#7 ·  Posted (edited)

 

I think BrewManNH's solution works.

 

Saludos

Edited by Danyfirex

Share this post


Link to post
Share on other sites

It does indeed - ( BrewManNH ) just tested - it. So did yours Danyfirex but I didn't want a load o ElseIfs ( about 150 to be more accurate )

Thanks all for the assistance - much better understanding of it now.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Similar Content

    • TheSaint
      By TheSaint
      I had a need, and so I developed.
      Before I did that though, I did a quick search of the forum, and found a few things, but none seemed to suit what I really wanted ... though to be honest, I did not investigate them deeply or search extensively. In any case, I am not very good at modifying the code of others, nor do I enjoy doing so, so in the end I decided it was best to start from scratch ... re-inventing the wheel perhaps, but a wheel I feel a certain degree of comfort with. I also thought about Maps, but don't know enough.
      _IniString Functions (was Ini_InMem)
      Ini in memory
      Settings INI - Read/Write once to the disk
      INI File Processing Functions
      ... sure to be others.
      As with all my stuff, feel free to use (no guarantees) or modify ... just give me credit where due.
      I always go for the quick & simple approach, as those who know me here, are well aware, so without a doubt, my code could be improved - sped up, RegExp used, etc. So feel free to do that, and convert into a proper UDF, if you want, following best practices etc, as I am sure others will appreciate it.
      Recently, I have come upon a need to extract data from an approximately 50 Mb downloaded Index file, just extracting the few elements I need, and storing them in an INI file. It is quite a time consuming process, especially on my underpowered Netbook, which is where I am using the program I built. I have been considering ways to speed up things. Two good sounding methods, out of several possibles, have come to mind - 1) RAM Disk and 2) Virtual INI processing. That last being a better option, when sharing code (program) with others.
      Another method, which I am currently using, that did give me some measurable benefit, was to download the almost 50 Mb Index file in Stages (i.e. 30 x 1.4 Mb roughly), extracting data from each in turn. I have also considered extracting to 10 (or 11) separate INI files, rather than the single large INI file (4~5 Mb), as things noticeably slow up as the INI file increases in size ... obviously due to writing time.
      I can't really speed up the extraction process, but that last method may speed up the writing stage.  However, it would require significant program changes, and perhaps not gain me much benefit. To complicate things, there are too many Section names (Index ID's) for the IniReadSectionNames command, so I have had to split them off into their own (read/write) line-by-line index file, and create code to deal with duplicates. When read, Index ID's and Titles populate a Listbox control in a user GUI.
      So at this point in time, it seems best to use the Virtual INI approach to gain a significant reduction in time taken. For my own specific use, with my slow Netbook, I may also use a RAM Disk.
      Due to the aforementioned INI issues, and lack of available specific data, probably because it is always  program concentric, I have created an ASCII Checker program, which I guess you can say, is AutoIt  concentric. Because others may also find it handy, I am providing it here. NOTE - As yet, I am only aware that Escape characters exist, but have not investigated or catered for them in any way.
      ASCII Checker.zip

      The Virtual_INI_UDF is still a work in progress, though I have done most of the functions now, with the working but incomplete _Ini_Test function, still requiring changes etc from the information gleaned by the ASCII Checker program.
      Here's something to play with meanwhile.
      Updated files (24th February 2017)
      Virtual_INI_UDF.au3  NEW
      Example.au3 (23rd February 2017)
      All pretty basic, but managed to load my 4 Mb INI file (seemingly ok, but took a few seconds) ... though I have only worked with much smaller testing ones so far.
      P.S. While I have done a fair amount of testing, it has been pretty basic, and mostly limited to the examples provided. Testing has definitely not been extensive.