[AccessD] Access XP Meltdowns

Wortz, Charles CWortz at tea.state.tx.us
Wed Apr 9 12:59:52 CDT 2003


Charlotte,

I have to agree with William, in that we have been using A02 for some
time now without any problems.  We quit using VisualSourceSafe for new
projects because we were having too many problems with it.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: William Hindman [mailto:wdhindman at bellsouth.net] 
Sent: Wednesday 2003 Apr 09 12:29
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Access XP Meltdowns

Charlotte

...been using AXP for a long while now in a variety of environments with
nothing like you describe ...but I'm an independent and don't use
SourceSafe so you might want to take a look there ...HTH :)

William Hindman
"War is an ugly thing but not the ugliest of things; the decayed and
degraded state of moral and patriotic feelings which thinks that nothing
is worth war is much worse. A man who has nothing for which he is
willing to fight, nothing which is more important than his own personal
safety, is a miserable creature and has no chance of being free unless
made and kept so by the exertions of better men than himself."  John
Stuart Mill

----- Original Message -----
From: "Charlotte Foust" <cfoust at infostatsystems.com>
To: <AccessD at databaseadvisors.com>
Sent: Wednesday, April 09, 2003 11:40 AM
Subject: [AccessD] Access XP Meltdowns


> Has anyone else seen frequent meltdowns on XP (SP-2) databases in 
> development?  I've seen this on both source safe mdbs and those 
> compacted out of source safe.  The original project seems to be ok, 
> but the copy I'm working on goes down in flames.  It appears that 
> malformed code can trigger an endless loop of this, and the backup 
> option only perpetuates the damage.  I'm seeing this at least once a 
> day on the app I'm working on, and it's driving me nuts because it 
> happens when I'm in the middle of creating new code, which naturally 
> is malformed until it's complete!  Aarrrggghhh!!!
>
> Charlotte Foust


More information about the AccessD mailing list