[AccessD] WIERD little problem

William Hindman dejpolsys at hotmail.com
Tue Aug 16 22:35:28 CDT 2005


Karen

..have you done a decompile ...ect.?

William

----- Original Message ----- 
From: "Karen Rosenstiel" <karenr7 at oz.net>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Tuesday, August 16, 2005 7:21 PM
Subject: RE: [AccessD] WIERD little problem


> Yes, that sounds interesting. It's a small office, and only 5 people would
> be using this database. I'd like to look at your programming if you could
> share it.
>
> Meanwhile...Why would I not be able to print a report for 1 date and not
> another. A puzzlement!
>
> Regards,
>
> Karen Rosenstiel
> Seattle WA USA
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
> Sent: Tuesday, August 16, 2005 3:53 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] WIERD little problem
>
> Hi Karen:
>
> Coming at this slightly differently... I worked on a system where if a 
> user
> stays on a station with no activity for say, 1 hour, the station, unloads
> the tables, closes the forms and places them back at the application login
> prompt. (This method was developed at a client's request who got tired of
> always discovering one of her employees had left the 'Invoicing' 
> application
> open, running on the station and had gone back into the warehouse or off 
> for
> lunch.)
>
> Would a process like this resolve similar db application issues before 
> they
> can develop?
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Karen 
> Rosenstiel
> Sent: Tuesday, August 16, 2005 3:14 PM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] WIERD little problem
>
> I have a simple little scheduling database, front end and back end. I 
> tried
> to print a report for tomorrow - a simple list - the database crashed. For
> some strange reason I cannot print the reports I need for tomorrow, 
> although
> I could print reports for different dates - just not for tomorrow. It 
> closed
> itself down and tried to compact itself and send a report to MS.
>
> At that point, I discovered that one of staff left open the front end with 
> a
> little popup form from which you can view or print the reports wide open. 
> I
> got her out of a meeting to shut down her open Access and then deleted the
> backup copies and the .ldb files. I could compact/repair the BE but not 
> the
> FE.
>
> Has anybody had anything like this happen before? Any suggestions? I need 
> to
> mention that I can't send the database to anybody for inspection because 
> of
> confidentiality restrictions (I work in a jail health clinic).
>
> Thanks in advance.
>
> Regards,
>
> Karen Rosenstiel
> Seattle WA USA
>
>
> -- 
> 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
> 



More information about the AccessD mailing list