Jim Lawrence
accessd at shaw.ca
Thu Jan 21 22:48:58 CST 2010
Hi Robert: I am in the process of upgrading a very large and complex Access application from 2002/2003 into Access2007, on a group of new Windows7 platforms so I read and reread your adventure with great interest... and with some degree of horror. I might try to restrict or at least slow the drive towards Windows7 so if the worse comes to the worse at least their office is not completely down. On the client's site, if that was not enough they have moved there server system to SBS2007 and all the desktops have been re-directed off the server. I have not been able to find a directory similar to XPs default user directory. This is causing some strange issues in which a user can have their desktop running on a number of computers; sort of like the old roaming profiles but more... I was upgrading an application on one system but found it was failing and leaving strange ghosts. It turned out that a user had logged into the same desktop I was using for testing some where else in the building... I do believe there is enough horse-power or memory to fix these problems but we shall see. Jim PS Access2007 and Access2003 do not play nice together on the same box... watch out for those references... -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert Sent: Thursday, January 21, 2010 6:35 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Observations of my short life with Windows 7 & Access .MDE Observations of my short life with Windows 7 (32 bit) & Access .MDE (Access 2007 Runtime) Comparing the above against a tried & true Access Program (Same as installed on Windows 7) In Windows XP 1) Performance: Much Worse Wow, what can I say. Just about every aspect of performance has dropped. Read / Write times have dropped, Query performance has dropped. I Think there must be some OS mechanics that has changed as it related to MS Acess, and has somehow effected performance. (Still Looking for Answers) 2) Stability: Much Worse In the last 10 years, I have never had a user with a corrupted FE until yesterday. Somehow the front end corrupted and every time ONE list box was requeried they would get this msg. (after the Error Access Would Crash)(replacing the FE Fixed the problem) "Error#: -2147417848; Sys Desc: Method 'Requery' of object '_ListBox' failed" Now, for some reason, the MS Access.exe is not always closing or closing fast enough and Windows 7 doesn't like it and wants' to send a message and restart the program. I now have reports of what I call "Hanging Chads" under process. (The MS Access.exe did not close) I have combed over thousands of lines of code in the last 4 days looking for any objects that are not getting destroyed, and I simply can't find any, but yet my program engine (Access) is not always closing under Windows 7. (No problems in Windows XP) Complaints of random complete crashes, which of course there seems to be no pattern too. I currently have about 11 Windows 7 beta testers, and over 350 long term seated Windows XP installation. So the data pool is not huge, but something seems to be going on here... Keep in mind, with the exception of the installer (I'm trying to use Saykey's Access 2007 Development Wizard (Thats another topic in and of itself)) which is based on the MSI engine) and the OS (Win 7), the program is identical to ones being installed on Windows XP machines (Wise and Sagkey Scripts for those) PS: Has anyone else notice the "Bug" with the MSI installer? With windows Vista and Window 7, MS added the great ability to redirect users shell folders. It's a fantastic "feature" however it completely break the entire MSI Installing engine.. I would love to know if this is a bug or an intended MS feature....? Anyway RANT OFF WBR Robert -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com