Erwin Craps
Erwin.Craps at ithelps.be
Wed Jul 9 15:47:01 CDT 2003
Microsoft has some paper on it. Please note that VB applications as a service are posible but not recomanded by MS. You can just write a EXE like you normaly would but with one major difference... No user communication whatsoever troug msgbox, forms etc... Totally blind. The reason why MS does not recomand to use VB for a service is that the VB runtime self could generate a user message via a form.... Thus locking your service within a trap. Only solution is terminating the service. But it should not be a problem if you carefully program. You would need to write some management interface to communicate with your service in some way. -----Oorspronkelijk bericht----- Van: Joe Rojas [mailto:JRojas at tnco-inc.com] Verzonden: woensdag 9 juli 2003 22:13 Aan: 'Access Developers discussion and problem solving' Onderwerp: RE: [AccessD] Access app for 24/7 usage? Does anyone have any good links on how to create a windows service using VB6? I went to visualstudiomagazine.com but had no luck. It didn't let me search the archives. :( Thanks! Joe R. -----Original Message----- From: Drew Wutka [mailto:DWUTKA at marlow.com] Sent: Tuesday, July 08, 2003 4:22 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Access app for 24/7 usage? Ditto. A vb .exe doesn't have anywhere near the overhead compared to Access running an .mdb. I can't count how many VB services I have running. Even ones that have a timer firing several times a minute barely show a second or two of CPU usage per day. The big trick with running services, is you want to make sure you don't hog too much memory (release stuff you don't need....when you can). Drew -----Original Message----- From: John Colby [mailto:jcolby at colbyconsulting.com] Sent: Monday, July 07, 2003 6:42 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Access app for 24/7 usage? I tend to agree with Arthur on this. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller Sent: Monday, July 07, 2003 10:22 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Access app for 24/7 usage? IMO, for rock-solid reliability you should choose VB and install the EXE as a Windows service. Presumably the data you're grabbing is emitted on a serial port or somesuch and is basically a text file that you parse. If so, that's not difficult code to write. As for creating a service, you can find material on that at the Visual Studio Magazine site. Arthur -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Joe Rojas Sent: July 7, 2003 10:01 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Access app for 24/7 usage? Hi All, I am going to be creating an application that parses the output from our telephone system and log it into an Access database. This application will be running on a server so that it can be up 24/7. What I was wonder is if an Access FE app will be OK running 24/7? Would I be better off creating the FE in VB instead? I think that it would be easier to get the data into the database if I use Access as the FE but I am more concerned with reliability. Many thanks, Joe R. This electronic transmission is strictly confidential to TNCO, Inc. and intended solely for the addressee. It may contain information which is covered by legal, professional, or other privileges. If you are not the intended addressee, or someone authorized by the intended addressee to receive transmissions on behalf of the addressee, you must not retain, disclose in any form, copy, or take any action in reliance on this transmission. If you have received this transmission in error, please notify the sender as soon as possible and destroy this message. While TNCO, Inc. uses virus protection, the recipient should check this email and any attachments for the presence of viruses. TNCO, Inc. accepts no liability for any damage caused by any virus transmitted by this email. _______________________________________________ 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 _______________________________________________ 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 This electronic transmission is strictly confidential to TNCO, Inc. and intended solely for the addressee. It may contain information which is covered by legal, professional, or other privileges. If you are not the intended addressee, or someone authorized by the intended addressee to receive transmissions on behalf of the addressee, you must not retain, disclose in any form, copy, or take any action in reliance on this transmission. If you have received this transmission in error, please notify the sender as soon as possible and destroy this message. While TNCO, Inc. uses virus protection, the recipient should check this email and any attachments for the presence of viruses. TNCO, Inc. accepts no liability for any damage caused by any virus transmitted by this email. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com