Is there a collection that works like a Dictionary? [resolved]

Hey Guys,
I saw somewhere on MSDN that there is a collection that works much like an array and a dictonary combined. Now I can't seem to find it anymore. Does anyone know what namespace this type of collection is.

What it needs to do is have the ability of going through the collection based on Index or Based on a Key. The most important thing is it has to have the ability to be multidemnsional or have the ability to store sperate values for just one Key or Index.

I will be using it to keep track of data I remotely receive using WMI. For each machine I want to be able to access the data from this collection and retieve data based on the position it is in inside the array based on what dimension of the array it is in. Somewhat like an excel speard sheet.

EX:
Key=Machine Name Mapped Network Drives Last User on Processes
SomeMachineName Drive U;Drive;z kevin colletion of processes

something to that effect. I have a custom class I created that uses a dictionary object that uses the machine names as keys and inside the vale for the key is the index of a sperate array that is multidimensional which contains information from my scans.

It's kinda hard to work with but it works. There must be something else out there in the collection namespace that can do what I am already doing but better.

Thank you :wave:

I've found hashtables in VBNet as useful as the dictionary object.

For Example:

VB Code:

'[i][size=1]initialize hash tables at the "form" level[/size][/i]
    Public Export_Log_Fields As New Hashtable()
    Public Export_Log_Mode As New Hashtable()
    Public OUT_FIELD_TYPE As New Hashtable()
    Public OUT_FIELD_LOC As New Hashtable()
    Public OUT_TYPE_LOC_FIELD As New Hashtable()
 
    Public Sub INIT_HASHTABLE()
        Export_Log_Fields.Add("total impressions printed", "total_impressions_printed")
        Export_Log_Fields.Add("total sheets printed", "total_sheets_printed")
        Export_Log_Fields.Add("total black only pages printed", "total_BW_imp_printed")
        Export_Log_Fields.Add("total color pages printed", "total_Color_imp_printed")
'[i][size=1]yadayadayada[/size][/i]
 
        Export_Log_Mode.Add("job status", "1")
        Export_Log_Mode.Add("record status", "2")
        Export_Log_Mode.Add("container id", "1")
        Export_Log_Mode.Add("job id", "2")
 
 
        OUT_FIELD_TYPE.Add("total_BW_imp_printed", "int")
        OUT_FIELD_TYPE.Add("total_Color_imp_printed", "int")
        OUT_FIELD_TYPE.Add("total_sheets_printed", "int")
'[i][size=1]yadayadayada[/size][/i]
        OUT_FIELD_TYPE.Add("page_range", "str")
        OUT_FIELD_TYPE.Add("job_data_number", "str")
        OUT_FIELD_TYPE.Add("job_queue", "str")
        OUT_FIELD_TYPE.Add("sent_by", "str")
'[i][size=1]yadayadayada[/size][/i]
        OUT_FIELD_TYPE.Add("rip_started", "date")
        OUT_FIELD_TYPE.Add("print_started", "date")
        OUT_FIELD_TYPE.Add("date_submitted", "date")
'[i][size=1]yadayadayada[/size][/i]
 
'[i][size=1]now the array index locations, 3 arrays of 3 types, int, string, date[/size][/i]
        OUT_FIELD_LOC.Add("pages_ripped", "0")
        OUT_FIELD_LOC.Add("rip_time", "1")
        OUT_FIELD_LOC.Add("copies_requested", "2")
        OUT_FIELD_LOC.Add("copies_printed", "3")
        OUT_FIELD_LOC.Add("total_sheets_printed", "4")
'[i][size=1]yadayadayada[/size][/i]
        OUT_FIELD_LOC.Add("job_name", "0")
        OUT_FIELD_LOC.Add("job_queue", "1")
        OUT_FIELD_LOC.Add("sent_by", "2")
'[i][size=1]yadayadayada[/size][/i]
        OUT_FIELD_LOC.Add("date_submitted", "0")
        OUT_FIELD_LOC.Add("rip_started", "1")
        OUT_FIELD_LOC.Add("print_started", "2")
        OUT_FIELD_LOC.Add("print_completed", "3")
'[i][size=1]yadayadayada[/size][/i]
'[i][size=1]now, indicate the output field name when looping thru the 3 arrays of varying type[/size][/i]
        OUT_TYPE_LOC_FIELD.Add("str_0", "job_name")
        OUT_TYPE_LOC_FIELD.Add("str_1", "job_queue")
        OUT_TYPE_LOC_FIELD.Add("str_2", "sent_by")
'[i][size=1]yadayadayada[/size][/i]
        OUT_TYPE_LOC_FIELD.Add("int_0", "pages_ripped")
        OUT_TYPE_LOC_FIELD.Add("int_1", "rip_time")
        OUT_TYPE_LOC_FIELD.Add("int_2", "copies_requested")
'[i][size=1]yadayadayada[/size][/i]
        OUT_TYPE_LOC_FIELD.Add("date_0", "date_submitted")
        OUT_TYPE_LOC_FIELD.Add("date_1", "rip_started")
        OUT_TYPE_LOC_FIELD.Add("date_2", "print_started")
        OUT_TYPE_LOC_FIELD.Add("date_3", "print_completed")
 
    End Sub

:wave:
-Hope this helps!
-Lou

you can also use the DictionaryBase class to create your own Dictionary Class...

What are the advantages of your suggestion?

A few weeks ago I came across, I believe, some sample code you wrote.
It looked good, but I didn't quite understand its functioning if, for example, all I needed was something to return a value if the key existed, or else return nothing.

Is this what you are looking for? (I use a couple of sorted lists as dictionaries)

Public g_StoreList As New SortedList
Public g_FileList As New SortedList

This is how it is listed in the Help Heap:

.NET Framework Class Library
SortedList Members

Quote:

---

Originally Posted by NotLKH

What are the advantages of your suggestion?

A few weeks ago I came across, I believe, some sample code you wrote.
It looked good, but I didn't quite understand its functioning if, for example, all I needed was something to return a value if the key existed, or else return nothing.

---

well if you want a dictionary type class... but need it to have some additional functionality (for example populating its contents from a database) then often times creating your own class is the way to go because they give you these robust base classes to inherit from... I need to know nothing about how to enumerate or any of the inner workings of a collection type class becuase its all brought up from the baseclass

that is just one example.. but pretty much ANYTHING you may want a dictionarytype class to do that it doesnt by default can be added into your customer class... while still getting everything from the base.

using a hashtables will no doubt be a useful answer in many situations also