Visual Basic&database, How to multitask Access\vb on 16 bit Windows

How to multitask Access\vb on 16 bit Windows

Author	Message
Andy Bal #1 / 3	How to multitask Access\vb on 16 bit Windows Not being an expert in either Access 2.0 or vb3 I guess this a rather simple question. Have a SQL Server reporting db that is accessed using in house developed Access 2.0 front end. Fairly big tables about 2million rows. We have tuned SQL pretty well and the worse response time is 5 minutes. This would be acceptable to the user only if they could do something else whilst the query is running - Access seems to take full control of the desktop whilst running the query. The client is Windows 3.1 , would 3.11 make a difference ? Can't consider using 32 bit client at this stage. Any ideas would be gratefully received -- Greenfell Computing Ltd
Sat, 11 Jul 1998 03:00:00 GMT

LarryMorr #2 / 3	How to multitask Access\vb on 16 bit Windows You can't. The Jet engine basically locks the workstation up until it starts receiving results back from SQL Server. Running Access 2.0 or VB3 on Windows 95 does the same thing. It does work on NT, although you know it. Using Access 7 in windows 95 largly eliminates the problem. says... Quote: >Not being an expert in either Access 2.0 or vb3 I guess this a rather >simple question. Have a SQL Server reporting db that is accessed using >in house developed Access 2.0 front end. Fairly big tables about >2million rows. We have tuned SQL pretty well and the worse response >time is 5 minutes. This would be acceptable to the user only if they >could do something else whilst the query is running - Access seems to >take full control of the desktop whilst running the query. The client >is Windows 3.1 , would 3.11 make a difference ? Can't consider using 32 >bit client at this stage. >Any ideas would be gratefully received >-- >Greenfell Computing Ltd
Tue, 14 Jul 1998 03:00:00 GMT

BBS News Us #3 / 3	How to multitask Access\vb on 16 bit Windows : Not being an expert in either Access 2.0 or vb3 I guess this a rather : simple question. Have a SQL Server reporting db that is accessed using : in house developed Access 2.0 front end. Fairly big tables about : 2million rows. We have tuned SQL pretty well and the worse response : time is 5 minutes. This would be acceptable to the user only if they : could do something else whilst the query is running - Access seems to : take full control of the desktop whilst running the query. The client : is Windows 3.1 , would 3.11 make a difference ? Can't consider using 32 : bit client at this stage. : Any ideas would be gratefully received : -- : Greenfell Computing Ltd Two solutions: 1. Use a multitasking operating system: NT, Win 95, OS2 2. Use async. queries under windows 3.1, WFWG 3.11 Art Yates
Thu, 16 Jul 1998 03:00:00 GMT

Page 1 of 1

[ 3 post ]