Charlotte Foust
cfoust at infostatsystems.com
Thu Aug 17 10:25:43 CDT 2006
If they're preset in the database, you can open the project properties from the Tools menu in the VBE and look at the general tab. Conditional Compiler arguments are at the bottom of the dialog. However, if they're being passed in from outside or are intended to be. You can also declare compiler constants in code. They're prefaced with a # as well. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Richard Lavsa Sent: Thursday, August 17, 2006 8:14 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Vberrorhandler download "trace logging code" Thanks, for the response.. Any way to tell what those specified conditions are? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, August 17, 2006 11:00 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Vberrorhandler download "trace logging code" The # signs are compiler conditional indicators. They tell the compiler to execute the If-End IF under specified conditions only. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Richard Lavsa Sent: Thursday, August 17, 2006 5:53 AM To: Access Developers discussion and problem solving Subject: [AccessD] Vberrorhandler download "trace logging code" Hello all, I was in a bit of a rush for the latest application I wrote so I didn't have a chance to fully document or put in all error checks, or for the matter the destruction of all objects. I remembered John, Seth, and Glen wrote a vb Error tool. When I finally remembered where it was and used it, it was great. Saved me a ton of time. However I do have a question. I enabled the "Insert Call Stack trace logging code". When the error traps are entered I see the code that writes to the external file however in forcing it to error out, I do not see an error log anywhere. I stepped through the code of which none of the code to write it out to a file was ever utilized. Not knowing what the # signs did in #IF and #End If statements I removed them for the particular sub that I forced to error out on and then got an undefined variable error. So my question is, what am I doing wrong with the "Insert Call Stack trace logging code"? It looks like the error log is supposed to be placed In the same location as the local database, but I couldn't find it? For curiosity what do the "#" signs do in the code, I couldn't find anything in the archives about this? Even if the trace logging doesn't work, I am very grateful for the portion of this tool that did work without any issues. It saved me hours of going back through and putting error traps in. Just wanted to pass my gratitude along to John, Seth, and Glen. Rich -- 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