Search results

Our current file server needs replaced (running Windows Server 2008 and highly usage) and we are likely to do so in 4Q. I don't have enough background knowledge to know about the total server costs (aside from hardware). Licensing and all that. Our 3rd party IT company is quoting between $12K...

That's the only sample I've seen that enumerates everything in their sample code. Thanks for the link. I'm cleaning up the last bits we've been talking about.

Before I post my full script in all its ugly glory.... @cheekybuddha - Why did you add the "TristateFalse as Integer = 0" line in defining the constants? That wasn't in the sample code I saw even if the help files and whatnot list all the various enumerations.

@cheekybuddha - That is because this code is part of a script written using VB Script that will be run to launch the database, not part of the database module code itself. It is that property/function that got me thinking about how many times objects were defined in my script. It got put...

Everyone, Thanks for the updates (and the rewrite)! I can understand the basics of object oriented programming but any time I run into a question the doubts spring up. Sorry for the copy/paste errors. I also had a find/replace issue that you pointed out that had been corrected but not before I...

Sorry, i didn't post the original code :) Here's a sample: If Not oFSO.FileExists(sLocalLog & "\startuplog.txt") Then 'Check if log file exists Dim fs, f Set fs = CreateObject("Scripting.oFSOtemObject") Set f = fs.CreateTextFile(cLocalFE & \errorlog.txt"...

That's what I'm trying to do! :) How might one trip over one's toes? The original code I'm referencing sets a new object inside of each clause of the If/Then statement.

So, I'm working on my App launch script and trying to streamline things. I would like to use one file system object for everything but I have no idea if that will cause problems or not. Here is some sample code. Not all variables are defined within this codeblock. Dim oFSO Set oFSO =...

I admit to being mildly irritated at one point in this process, but, the coffee is kicking in now. My apologies. :coffee::D Thanks for your help.

That's what it appears I'm being told. Am I wrong? I had to answer my own question ;) If I search for "Wscript.FileSystemObject" on this forum, the only hits I get are this thread. If I search for "Scripting.FileSystemObject", I get a whole lot of hits.

That's not really the definition of a typo is it? A typo is me spelling cat "CATT". A typo is not me spelling dog "CAT". This was a very long way around of saying that there I had the wrong idea. Which is what I was going for in the first place. So, I'll take a stab at answering my own...

You are correct in that it didn't work. But I don't know the typo. Changing it to Scripting.FileSystemObject works fine. So what is the typo/problem?

I was just quoting a single disconnected line of code. Just in case it's confusing, here is the full potential property taken from this page. Public Property Get FSO() As Object Static f As Object If f Is Nothing Then Set f = CreateObject("Wscript.FileSystemObject") Else 'return...

Microsoft help docs use scripting.fileystemobject. I also have some code samples that use that. But, I also have some codesamples that use wscript. I've seen posts on here using both. I know that wscript is a windows module that translates vbscript. Is there any appreciable difference...

Thanks! Getting my coding sea legs back under me again. :coffee::giggle:

Ah, makes sense. A little snipping and pruning and modifying and we get the following code (still using Select Case True instead of an OR in an If/Then). Edit: To address your other concern. IF this code is working correctly, there should only ever be one hanging session. But, even if there...

@theDBguy - Thanks! didn't mean to sound snarky at all. :) I did have a tangential question...in your code suggestion you used Nz to encapsulate the dlookup. Reason?

It definitely could use some optimization. I'll look at it again. The main question is about Dlookup, Dcount, etc on an ever expanding table of records.

@theDBugy - If I am remembering correctly, one of the benefits of Select Case True is that the rest of the cases are not resolved when a case is found true. But, I could be wrong.

Thanks for the info. Do all fields used in a DLookup, Dcount, etc function need to be indexed?