Hi ebgreen,
thanks for forcing me to think and talk about my pet more clearly! The goal of the first
contributor was to get scripts/howtos from this forum fast - no complicated search process,
no fear to miss the gold because you selected a 'wrong' keyword. I have my own material
organized in a way that is not bad (ok, sometimes I write something again, because another
computer isn't available at the moment or I forget which project that particular function
was used in), but it is difficult to integrate other people's code/postings/docs. Fredledingue's
description of his practice made me realize that
a centralized approach would have to be maintained correctly and wouldn't be
usable if the contributers wouldn't adhere to very specific rules of classification
a localized approach would allow each person to take what she needs and to
classify it according to his own scheme (that doesn't mean there couldn't be
some proposals/discussions about categories and their order)
I don't want to critize the order/structure/categories of this forum - it's a forum:
you get some 10 main categories and below that a chronological list of topics
(normaly a question and some answers). Finding something which isn't on the
first two pages and hasn't got a carefully worded subject means a full text
search - in my opinion just the opposite of accessing categorized data. Just
because I know that I wouldn't come up with a 'one size fits all' and easy to
apply scheme makes me think: each to her own.
I don't think that coding style would be a problem: if you get something helpful
fast, you can spend a little time to rework ('refactor') the code - and you don't
have to discuss it with the original author.
From what I learned about the xml format of iCodeLibrary, a contribution
could look like this (a 'normal' posting, just VBSR as a marker in the subject)
Subject: VBSR Create ADO Connection
Author: ehvbs
Keywords: database, ado, connection
Description:
Creates an ADODB.Connection according to the information in aParams. aParams(0)
is the type (MDB, TEXT, ...), the following paramaeters depend on this type - e.g.
Param( 1 ) is the directory with schema.ini and data files for TEXT ...
Function newAdoCN( aParms )
Const csODBVers = ""
Dim oRVal : Set oRVal = Nothing
....
oRVal.Open sCNStr
Set newAdoCN = oRVal
End Function
Sample usage:
Dim oCN : Set oCN = newAdoCN( Array( "text", ".\" ) )
for accessing the current directory as a poor man's sql server.
The user would select all + copy [I have to test this for code tags ...] and the hta app
would put this into the mdb readable by iCodeLibrary.