Significant Issues: Access

[rivsys]

I run XP x64 and Office 2003 on an x64 box with multiple monitors. My
configuration has two hardwired monitors attached to an ATI X1900 XTX and a
third monitor is accessible using the Maxivista x64 beta to take control of
the monitor attached to my testing machine.

I am seeing a number of serious issues when running Access across multiple
monitors. For instance, in a two monitor configuration running the main
Access window on Mon1 and the VBA window on Mon2, Access abends to desktop on
Form Save, and occassionally on Debug/Compile. Also, under certain conditions
I get a C++ runtime error, but I haven't sat down to fully document the
events leading up to the crash.

IMPORTANTLY, NONE OF THESE ISSUES OCCUR WHEN LIMITING ACCESS TO RUN ON MON1
EXCLUSIVELY.

Does anyone else have any observations of this sort? I am a strong proponent
of multiple display workstation environments and have always felt that
Windows generally could do a much better job of exploiting this capability.

 

[Arvin Meyer [MVP]]

I see more crashes when running with multiple monitors, especially using
CRTs. I believe that most of these are caused by either the video drivers or
the video cards. Access is more susceptable because of the larger files. I
also have the same problem with large graphics files. So far I haven't lost
any more than my temper. I like using multiple monitors as well, and the
crashes are infrequent on my machines now that I am using 2 LCD displays. My
machines are all Pentium 4 32bit, not 64 bit. One is a 3.0 GHz, 1 GB of RAM,
the other is a Duo Core 3.0 GHz 2 GB of RAM. The 2 GB machine has an ATI
Radeon X300 Graphics card and crashes the least.
--
Arvin Meyer, MCP, MVP
Free MS-Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[dbahooker]

have you run http://officeupdate.microsoft.com?

you could always use Access Data Projects; and then you could use real
development tools-- like Query Analyzer, Enterprise Manager; Sql Server
Management Studio in order to develop in the database

I reccomend putting your efforts into SQL Server; MDB is just a
flat-out joke.

it's not stable; it's not reliable.

people always run out and come up with excuses; but the bottom line is
that MDB is a piece of crap.

-Aaron

 

[rivsys]

I suspect the issue is with XP x64, and perhaps ATI's 64 bit driver. But as
the issue seems isolated to Access (even the other applications in Office
behave themselves) I am less inclined to point the finger at ATI.

Once again the facts:

1 - Access is the only application that I have observed crashing to the
desktop under multi-display usage.

2 - I have 4GB Ram and 512MB of video memory. Memory is not an issue.

3 - I have been running multiple monitors for years, both CRT and LCD. I
have observed this only since switching to a 64 bit system. CRT or LCD should
make no difference whatsoever.

I would be surprised if I were the only user on earth seeing this...

 

[dbahooker]

yeah; so in other words; dont use MDB across a wireless network.. don't
use it with dual monitors; don't use it with ATI and dont use it with
x64.

and oh yeah; don't run it across a network since performance sucks.

in other words; what I'm heading is that MDB is too unstable for real
world use ANYWHERE?

that's what i've been saying for years