Replies

Hans,

This is getting “interesting”… I checked the code carefully and did not find any unqualified references. Investigating further, I opened up Task Manager and watched it as I stepped through my “Send Mail” routine. If Outlook was already open, things work fine… the existing instance is detected and used and left open at the end. However, if Outlook is not initially open, my routine generates the instance, but when it executes to the appOutlook.Quit command, the instance remains in Task Manager. When I run the routine again, GetObject does not see this residual instance, so CreateObject generates another one. appOutlook.Quit doesn’t close this one either. This continues as more e-mails are sent…

Here’s where it gets interesting… I Googled “multiple instances of Outlook” and found this article which describes an apparent bug in SpamBayes (which I have running as an add-on to my Outlook) causing multiple instances of Outlook when “mailto” links are used. They claimed that if SpamBayes is disabled in Outlook (Tools…Otpions…Other…Advanced Options…COM Add-Ins…), the problem goes away. On a whim, I tried this and, lo and behold, my multiple instance problem went away! (Curiously, the created instance is not removed from Task Manager immediately after executing the appOutlook.Quit command but is removed once the subsequent End Sub command is executed.)

That’s the good news… The bad news is that now that SpamBayes is disabled, I get that annoying “A program is trying to access e-mail addresses you have stored in Outlook. Do you want to allow this? … ” message… (attached) for each e-mail generated. (SpamBayes apparently circumvented this message.) Is there any way yet to disable this message at the end-user level? (I’m checking with our Microsoft Exchange Server administrator to see if they can do something about this at their level; e.g. one of the solutions in your post 488173.)

Thanks.

The saga continues…

I’ve tried publishing this form to a Public Folder. When I navigate to the folder, the form indeed appears at the bottom of the Actions menu (a “curious” arrangement) as advertised. The form opens fine for me. However, one of my colleagues does exactly the same thing (I watched him do it) — he gets to the public folder and highlights it, but the form does not appear in his Actions menu.

Is there some switch in Outlook that needs to be turned on to permit form use? Or is there a setting in the form itself (that I haven’t found yet) that permits “public” access? Or something else?

Thanks.

Perfect!!

Thanks.

Hans,

The user-level security on this database doesn’t let me run the routine in the article you referenced. However, I found a variation of this routine (285822) that acts on the current database rather than an external one which circumvented the permissions hurdle. The routine did list the culprit user (plus me, of course).

I’ll see what the network administrator is willing or able to do for me.

Thanks for the help.

Hans,

In my search, I did run across this article. At first I thought I couldn’t use the code since Access wouldn’t let me save/design anything (since it “thought” another user was using the database). However, I found I could enter the code from this article an run it — I just couldn’t save the module. I suppose this might be a handy utility to have in the database (ahead of time), for situations like this…

Okay, now that I know who Access thinks is using the database (besides me) — and I’ve confirmed that he actually isn’t, how do I clear him out? One thing I’ll try when he comes in tomorrow is have him log in to the database and exit (gracefully) and see if this “clears his name”. Any other ideas (particularly if this doesn’t work)?

Thanks,

Luke –

Thanks for your ideas.

I use STS but none of the users do. I haven’t had a problem (so far) with Access not shutting down properly when using STS.

The backend is on a site-wide server “farm” — I doubt I could talk the administrators into rebooting it just for me… If that’s the only option, though, I may have to resort to that…

Hans,

Here’s the scrubbed file (passwords removed; names changed). I tried it here at home and it seems to work okay (reasonably quickly) when first opened. Now I’m wondering if it has anything to do with the file (at work) being located on a network share area… Nonetheless, if you see anything in the file that might cause this behavior, that would be a great help.

Thanks.

Hans,

Thanks for the tip. I added the lines and voila! It ran quickly as it should. BUT — I saved, closed, and re-opened, ran it again and it was back to it’s sluggish self. It seems that if I go into VBA editor, change something (like this) or something else that’s innocuous it starts running (and continues to run) fast, but reverts to its bad habits the next time I open the document. Per chance, does this provide any hint as to what might be going on?

Thanks.

I was wrestling with this problem last week and came up with a solution that may help in some situations. The challenge is to get a multiple column down-then-across subreport to work — as noted in this thread, unless you specify across-then-down, you don’t get the multiple columns — if the content extends past the end of the page, you get one column on the first page and a continuation (still one column) on the second page, etc.). However, things work more as you would expect if you specify across-then-down for the subreport multiple column page layout. Unfortunately, this format often doesn’t work for multiple column report content.

I have found that if you set the Can Grow property to No for the subreport control on the parent report and size the control to fill the physical size of the page (this can be a significant limitation), then the subreport will show multiple columns in the down-then-across format. The significant limitation is that if you have more subreport content than what fits in this fixed-height subreport control, the excess will not be visible. Nonetheless, this may be helpful if you know your content will not exceed one page (with multiple columns).

Thanks for the ideas. This is a little over my head, coding & scripting-wise, but I’m always up for a little continuing adult education! I like the way that if I copy your URL “http://jeffersonscher.com/Off2007/sc.asp?i=wo1-popular” into a fresh browser window and try to go to it, I get a warning message. That’s exactly what I’m looking for for that half of the problem.

Can suggest some resources that would help me get moving up the learning curve on ASP or PHP scripting, to a level that would be necessary for this sort of application? Thanks so much!!

Here’s what you need (note: you don’t need to open the reports):

Public Sub GetReportDescriptions()

Dim objCurrentProject As Object
Dim objAllReports As AllReports
Dim objReport As AccessObject
Dim strReportDescription As String

Set objCurrentProject = Application.CurrentProject
Set objAllReports = objCurrentProject.AllReports

For Each objReport In objAllReports
strReportDescription = CurrentDb.Containers(“Reports”).Documents(objReport.Name).Properties(“Description”)
Debug.Print strReportDescription
Next objReport

End Sub

You may be able to simplify this further by simply stepping through the Containers(‘Reports”).Documents collection.

For those situations where you do need to open the report to look at other properties, you can avoid the “flickering” by specifying acHidden in the DoCmd.OpenReport statement.

Hans,

Dang. I thought there might be some obscure Size property or something. Oh well. A variation on your suggestion that I think I’ll try is to start moving tables over to a backend database and establish linked tables. This way I’ll hopefully see how one grows while the other shrinks and still have a functioning database in the process. Probably not a bad thing to do anyway.

Mark,

No, it’s a single-user all-in-one database. See my response to Hans.

Thanks, Hans. That should take care of it. Perfectly.

Since my original post, I’ve noticed that this progress dialog sometimes remains on screen even when I’m not moving quickly between records (it seems to also occur when the form being updated does not have the focus). More disturbingly, when it is left on the screen and I quit Access (the only way I’ve figured out to get rid of it), I get a “Microsoft Office Access has encountered a problem and needs to close (yadda, yadda, yadda)…” error. Avoiding the dialog entirely with the registry tweak will hopefully prevent (the need for) this less-than-graceful exit from Access.