This doesn't only happen with db's created with earlier versions of
Access. Opening and closing the db helps for only a few minutes before
it starts to happen again. Same goes for compact/repair.
Not entirely sure when this started happening but I wonder if it could
possibly have something to do with something that happened a few weeks
ago: I was checking out chart creation in Access forms and pivot table
view. I can't remember exactly what, but I clicked on something and
got a message saying that feature was not installed. I told it to
install and I think there was a crash in the middle of the
installation process. Everything seemed to work okay immediately after
that and I didn't need to do anything more with charts, so I forgot
about it.
Maybe I need to reinstall Access? If I do so, does that count as a
second computer toward the maximum # of installations on this
license?
Thanks for your help.
Somewhere I read that this had to do something with being hooked up to
a networked PC. So I changed my default printer at work to PDFCreator
instead of the network printer but the issue still occurred.
I would love to know how to make this go away.
Steve
That is pretty much exactly what I'm experiencing. I'm on a wireless
network for internet purposes, am not using network file sharing, and
my printer is on a local USB connection. So I don't think the
networking is the issue. I tried running an Office 2007 installation
repair and that didn't help at all. Still wondering if reinstalling
Access or Office needs to be the next step.
--
AG
Email: npATadhdataDOTcom
"septimus" <oveng...@yahoo.com> wrote in message
news:96aa3628-5497-41e1...@l36g2000vbp.googlegroups.com...
I take it you are referring to MS Office 2007 SP2? I checked an it is
not installed. We are not using a SQL server backend. It is a split
Access DB with the backend on a share drive. Operating system is XP.
Steve
Not sure about SP2, I tried to figure out whether I had it but I
haven't been able to find a way that works. Is there an easy way to
check whether it's been installed?
I did try reinstalling Office and it doesn't seem to have done much to
solve the problem.
Thanks.
--
AG
Email: npATadhdataDOTcom
"septimus" <oveng...@yahoo.com> wrote in message
news:e8c448ec-8535-45f8...@l30g2000vbn.googlegroups.com...
On Apr 22, 3:47 pm, "agiamb" <NOSPAMagi...@newsgroup.nospam> wrote:
> Office button > Access Options > Resources > About
>
> --
>
> AG
> Email: npATadhdataDOTcom
>
> "septimus" <ovengra...@yahoo.com> wrote in message
>Ah, thanks AG. I do have SP2.
>So what else could be causing this?
OK assuming this is not a split database, then the next couple of things to
check are if you're using an unattached or network printer?
Access constantly queries the printer for information about control layout
for both forms and reports. So if a printer is offline or not attached, or
is a network printer, this can be a source of delays .
In fact as a general Rule I now own set my default printer to a local
default PDF printer to prevent the above problem.
Another option to turn off is track name auto correct, as this can over time
be a source of delays during development - so I would disabled this feature
also.
And while your database may not be split, it's possible that you have
several table links in the table view that are network based or linked to
external data sources. Thus again this has been known to be a source of
delays during development.
If the above idea does not fix this, then work you way though the list here:
http://www.granite.ab.ca/access/performancefaq.htm
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenos...@msn.com
> OK assuming this is not a split database, then the next couple of things to
> check are if you're using an unattached or network printer?
> Access constantly queries the printer for information about control layout
> for both forms and reports. So if a printer is offline or not attached, or
> is a network printer, this can be a source of delays .
>
> In fact as a general Rule I now own set my default printer to a local
> default PDF printer to prevent the above problem.
>
> Another option to turn off is track name auto correct, as this can over time
> be a source of delays during development - so I would disabled this feature
> also.
>
> And while your database may not be split, it's possible that you have
> several table links in the table view that are network based or linked to
> external data sources. Thus again this has been known to be a source of
> delays during development.
>
> If the above idea does not fix this, then work you way though the list here:
>
> http://www.granite.ab.ca/access/performancefaq.htm
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
2. I've already turned off auto-correct and that doesn't seem to have
worked. Shame to lose that feature, though it seems buggy to me
anyway. When I had it turned on, I changed the name of a query and it
very nicely changed all references to that query throughout the
database. But then when I tried to run a query from VBA I started
getting parameter messages looking for the old query name.
3. You're right, I had some linked tables. Wasn't using them but they
were still in the navigation pane. I've removed them now. So far so
good, but time will tell.
Thanks for the help.
On Apr 23, 6:26 am, "Albert D. Kallal" <PleaseNOOOsPAMmkal...@msn.com>
wrote:
Update: the performance problem seems to have disappeared. I have not
always had my printer connected or set my printer to PDF, so I think
the linked tables were the culprit. No trouble since I removed them.
Thanks again to all.
Steve