[AccessD] Yet Another Access 2007 & Win 7 Bug -- Nasty

I am not seeing them Rocky, but I only have one PC with Win 7 at work
(mine!!).

My apps are in a2k3

Max
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Friday, March 19, 2010 1:20 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Yet Another Access 2007 & Win 7 Bug -- Nasty

Do you think the same kind of problems will occur with A2K3/W7?

R 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert
Sent: Friday, March 19, 2010 6:10 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Yet Another Access 2007 & Win 7 Bug -- Nasty

Been dealing with yet another program bug after switching the same program
that ran fine on Win XP to Window 7. I was getting this error on 2 different
section of the program. (There may be others but we have not found them
yet.)

Design:
 Form / Sub form design. Sub form based on simple query with 4 tables. 3
query based functions. Sub form OnCurrent event sunk to re-query some list
boxes on main form. (Error persist when removing the OnCurrent event)

   Imbedded Query Function Example:
       GetOnOrderAmount([tblInventory.InventoryID],[Location])

Symptoms:
  Intermittently; when a user moves from one record to the next 2 things
would / could happen.
	1) Throws 2 different errors (2465, 2424) and even though there is
error handling in place it would crash Access
	2) After trapping (and throwing a DoEvent after the error) for the
specific error(s), I could prevent Access from crashing. 
		a) when the error would occur; the field that had the prev.
focus would change to "#Name?" 
		   and lock up the entire database unless the user would
click back on that exact record.
		b) I could cause the error by moving between records
rapidly. I could always reproduce the error in just a few
		   seconds of doing this.
		c) Users said it was more likely to happen if using the
record selector for moving between records.

Pictures of what that looked like.
http://i40.tinypic.com/n6ztcl.png

http://i44.tinypic.com/2929mx1.png


Corrective Measures.
  After much trial and error, I discovered that if I completely remove **
ALL ** the imbedded functions in the query(s)
  and move them to the actual sub form field(s) the problem completely went
away.. 

   =GetOnOrderAmount([tblInventory.InventoryID],[Location])

Just thought I would add to the continuing saga of Access 2007 and Windows
7.. I can say this with confidence. This is a lethal combination for anyone
utilizing an Access .mdb(e) as a front end program. 

If your program has ANY complexity to it, I can pretty much guarantee you
will encounter some of the strangest errors and anomalies you have ever
experienced with Access before... ;-)  Garbage is what it really is, utter
garbage....


WBR
Robert


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com