[AccessD] Dlookups. your opinion please.

"the first thing I would do is convince the owners that the db needs to be rewritten from scratch, if at all possible"

oh yeah, that is not only possible, it is going to happen as that is precisely what we recommended to the client.  Tell us what data you have, tell what outcomes you need and we will (re)build it.  The current model is too risky and flawed for us to be bothered with. It will take longer to debug it then it would to rebuild it into a nice tight supported app.

Sadly for the client, (and good for us), we currently have about 4 months worth of work in the queue so this is just a(nother) band aid on the worst of their problems.  basically they want a quick and dirty fix to get them thru the next couple of reporting periods until we can rebuild it properly.

Not the greatest solution I admit and it comes with risks, but the client is aware of this and is ok for now. This is definately something middle of the road temp to keep most folks happier, if not happy.

thanks for everyone's input. It is really appreciated.

cheers
Darryl.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
Sent: Tuesday, 23 September 2008 11:55 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Dlookups. your opinion please.


Darryl, the first thing I would do is convince the owners that the db needs
to be rewritten from scratch, if at all possible. Unless you're auditing
this thing regularly, there is no way to know when it's generating errors.
If they're iffy on that, I'd work hard to find an error and draw it to their
attention. Say, it reports that you have 100 widgets in stock when you
really have 150, so you missed that big sale to an important client
yesterday because she really needed 130, but because you couldn't supply the
full amount, she went someplace else. Find an error.

Second, domain aggregates aren't bad. Some say they're slow and that would
include me, but um... others thing I'm daft on that one. Gustav (I think it
was) said a simple index on the column takes care of the performance
problem, and if that's the case, that would be fine in most cases -- but in
yours, it might not. Adding an index might blow something up! ;) <drama>

But domain aggregates, in an of themselves, are just fine. With so much to
fix, I don't think I'd give them priority if it were me.

Susan H.


> Hi All,
>
> I have, ummm, inherited a database (SQL Server Back, Access Front) at
> work.  Frankly this thing is a disaster waiting to happen and since the
> guy who built has left (he used to admin it, and I suspect there were
> regular band aid repairs and updates to keep it all steady) the actual
> users are having no end of bother and bugs with it.  anyway, I digress...

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

This email and any attachments may contain privileged and confidential information
and are intended for the named addressee only. If you have received this e-mail in
error, please notify the sender and delete this e-mail immediately. Any
confidentiality, privilege or copyright is not waived or lost because this e-mail
has been sent to you in error. It is your responsibility to check this e-mail and
any attachments for viruses.  No warranty is made that this material is free from
computer virus or any other defect or error.  Any loss/damage incurred by using this
material is not the sender's responsibility.  The sender's entire liability will be
limited to resupplying the material.