Recent content by BobRodes

I've been learning Ruby ... An unforeseen consequence of the information revolution has been the exponential propagation of human error.

The correct wording of the sentence is this: An unforeseen consequence of the information revolution has been the exponential propagation of human error.

The Oxford Style Guide uses the serial comma convention, while the Chicago Manual of Style, the AP Stylebook and The UPI Stylebook do not. However, in those that do not, there is a specific exception to clarify ambiguities. This is entirely clear, which is no doubt what ought to have been...

To expand on strongm's post (seems old habits die hard): "Grammar" is defined as "The whole system and structure of a language or of languages in general, usually taken as consisting of syntax and morphology (including inflections) and sometimes also phonology and semantics." Of these...

Rather than being simply a colorful use of a certain Australian marsupial for an object reference as one may often find on certain of these forums, "WOMBAT" is also an apparently British acronym standing for "Waste Of Money, Brains And Time." One may thank Mr Charles Stross for letting the cat...

Ok, I do have a question. What have you tried so far? An unforeseen consequence of the information revolution has been the exponential propagation of human error.

As it turned out, one of the procs had a reference to one server that had the password stored incorrectly. I found it by removing chunks of the proc and attempting to execute the rest using the defective login. Eventually I narrowed it down to a particular server reference, and from there I was...

Looking further, in the log the error state is 8, "password did not match that for the login provided." I'm not able to see where the password would be provided, since I've already logged into the server. An unforeseen consequence of the information revolution has been the exponential...

Sorry I forgot to put that in. "Login failed for user 'username'". An unforeseen consequence of the information revolution has been the exponential propagation of human error.

I have two stored procedures (actually several, but it boils down to this). I can execute both of them under my userid without problems. We're using a specific userid for running reports. With this userid, I can execute one of the procs and not the other, and they both appear to have the...

As it turns out, my question has its basis in a misunderstanding. When I first got my Export method to work at all, it was with this format: public void Export<Category>(someCategoryList, "C:\Temp2\myFile.txt", 0) I wanted to know how I could plug different values in for <Category> without...

I have a generic method, so: public void Export<T>(List<T> exportList, string filePath, byte fileType) where T: class There are two possibilities for <T>: <Category> and <ProductSupplier>. Previous to this call, I have a method which uses reflection to get a List<T> object (at least, I think...

Reminds me of Java's "Insert, Update and Delete" objects. An unforeseen consequence of the information revolution has been the exponential propagation of human error.

<Very modest owner I am sure Well, I don't know. Perhaps he was commenting on the ineffable ubiquity of the Tao... An unforeseen consequence of the information revolution has been the exponential propagation of human error.

<I wonder if 'obamacare' will become an adjective to describe misbegotten, or mismanaged IT Projects that were knowingly released incomplete and insufficiently tested ? We already have a name for those. They are called "IT Projects". An unforeseen consequence of the information revolution...