John Bartow
jbartow at earthlink.net
Thu Feb 13 10:19:28 CST 2003
Hi Richard: I tend to only write things to the registry that pertain solely to the user or machine it resides on. For instance particular user settings for data defaults, I store form coordinates there so the forms always go where the specific user placed them, etc. I also include routines to clear those settings. If it is something that pertains to anyone using the database (FE/BE scenario) from any PC then I store the piece of information in the database. Thats what I do with mileage rates, local tax rates, company name, etc. This is generally done with a table (that will probably never have more than one row) and a column for each value. There are more elegant ways but this works and it also opens up the possibility of having more than one row with more than one value for each. So if 2 different departments have two different mileage reimbursement rates this works out nice. (happened to me-once) BTW I include a key column and always refer to it when looking up the value. HTH JB -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Wednesday, February 12, 2003 6:44 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] SubReports no longer printing >>I get an error when I try to open them from the properties window When you try to open the links wizard? What error do you get, and do you get it only on that machine? Charlotte Foust -----Original Message----- From: Elam, Debbie [mailto:DElam at jenkens.com] Sent: Wednesday, February 12, 2003 10:27 AM To: 'accessd at databaseadvisors.com' Subject: [AccessD] SubReports no longer printing Yesterday, one of my users no longer saw any information on her subreports. The info was there, and other users of the same database can see the information. The FE is Access 97 and the BE is SQL 2000. I can still connect to the data, and can even run the subreports alone and get data. I suspect the parent child field linkage is to blame and I get an error when I try to open them from the properties window. I have tried re-loading access to see if that could cure the problem, but I still have the same problem. I have looked in the MS Knowledge base, but so far I have not found anything like this. BTW: We had a virus infestation hit us on Monday, but this user does not have the telltale files of the virus. Our virus software can detect that particular virus, and it did not. Still, the timing and weird behavior is a little coincidental. If anyone is familiar with the effects of the Pate virus on Access that may be helpful. Debbie - JENKENS & GILCHRIST E-MAIL NOTICE - This transmission may be: (1) subject to the Attorney-Client Privilege, (2) an attorney work product, or (3) strictly confidential. If you are not the intended recipient of this message, you may not disclose, print, copy or disseminate this information. If you have received this in error, please reply and notify the sender (only) and delete the message. Unauthorized interception of this e-mail is a violation of federal criminal law. This communication does not reflect an intention by the sender or the sender's client or principal to conduct a transaction or make any agreement by electronic means. Nothing contained in this message or in any attachment shall satisfy the requirements for a writing, and nothing contained herein shall constitute a contract or electronic signature under the Electronic Signatures in Global and National Commerce Act, any version of the Uniform Electronic Transactions Act or any other statute governing electronic transactions. _______________________________________________ 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