Replies

It really wasn’t about having to store the value, it was more about having to know the value at all! Also, I thought that would make it easier to use. For example, take this bit of code:
RunCommand getValue(“acCmdZoom75”)

I can put a DLookup in the getValue function to retrieve the actual numeric value. But if there was a way to convert the string directly to the intrinsic constant, it would be faster and cleaner.

Oh well, it was thought.

Unfortunately, I can’t offer you much more help, as my experience with manipulating graphic files is somewhat limited.

Instead of “Me!TOrderID”, you might try “Screen.ActiveControl”.

I know where to find the values, I was just looking for a way to do this so I didn’t have to find the values! It looks like I may have to create a constant/value table.

Since I don’t have any large reports like Judy mentioned (that take 60 seconds to display), I can’t say this will work. That’s why I said it may be possible to put it in a report’s event. This event might still fire before the report displays. Unforunately there is no AfterReportHasDisplayed event!

I just discovered an interesting fact. Compacting a database that contains images ADDS(!) 4KB for each new image that has been stored. Don’t know why, and can’t find any documentation in MSKB about this. All we know for sure is that Access is lousy at storing images. I’d really look hard at a redesign.

I think what you are looking at is different than the Recycle Bin. The unerase utility just goes out to find all instances of a deleted file in your directory (that is filenames that contain a ‘?’ as first character). These may or may not be recoverable. I wouldn’t worry about it.

Yes I could do that, but that’s what I wanted to avoid, having to determine what the codes are. I can envision other scenarios, and it would be nice to be able to specify a string containing a constant name which could be evaluated into the property value. For example, if you use the StrConv function in an SQL statement, you can’t use the intrinsic contstants such as vbProperCase. You have to remember what the code is. It would be nice to be able to get it using a function, something like:
getConstant(“vbProperCase”)

I assume your code looked like this:
docmd.hourglass true
docmd.openreport ……..
docmd.hourglass false

You have to realize that Access doesn’t stop processing the procedures while the report is opening. It spins that off as a separate task, then continues on with the next line of code (turning the hourglass off). You might try turning the hourglass off in your report code, but I’m not sure that would help much.

A “splash” screen is what you often see as the first screen in an application (showing title, etc.), that automatically disappears after awhile. Merely create a form that has on label on it, and put in nice large letters some caption to the effect of “Please be patient, the report is processing!”. In your form’s TimerInterval, put a value of 5000 (this is 5000 milliseconds, which is 5 seconds) or whatever value you want. Create an Event Procedure for the OnTimer event with the single line of code:
DoCmd.Close

That’s all it takes. If you get real ambitious, you could pass a parameter in the form’s Arguements property that sets the TimerInterval accordingly.

You said you were storing 620MB of images. Was that the sum of the sizes of the original images, or was that the size of the Access database after the images were loaded?

I’m not sure whether you questions was a general question on using a global function or specific to this function? The nature of your function (Using the IsOpen function to check whether a form is opened) would seem to indicate you are calling this function from yet another form? Perhaps if you could explain the nature of the function call, I could give some clues as to how to make it a global function usable by any form.

As for some specifics, you might want to use Select Case instead of all the nested ElseIf statements.

You might try putting a DoEvents right after the DoCmd.Hourglass. Sometimes this helps.

As for not wanting to use a message box, why not just create a “splash” screen with a “Waiting for report to load!” message. You can set the TimerInterval for as long as you want, and put a DoCmd.Close in the OnTimer Event.

You could try the forum in Compuserve.

http://go.compuserve.com/msdevapps

(This probably didn’t come out right, I was trying to mark it as a clickable URL. How is this done?)

In this situation, I want to store a user option for a Zoom setting for previewing reports. In the option selection form, there would be a combo box, which would contain the string names of the runcommand zoom constants, that is: “acCmdFitToWindow”, “acCmdZoom75”, “acCmdZoom100”, etc. So, I would store the string name (not the numeric equivalent). Then when it comes time to run the report, I want to convert the string name to the numeric equivalent so I can use it with RunCommand.

Yes, I know I can store the numeric value, but then I’d have to dig-out the values (ex., acCmdZoom75=241), and I wanted a method in which I didn’t have to do that. After all, isn’t that one of the benefits of intrinsic constants?

Thanks. Most of the time it isn’t a big deal, but I was trying to following the exchange you had with Jim Dettman in my “Access XP” thread (which has 36 messages), and it was a real chore!