Inherited db part 2

[Ricardo]

Hi Again!,

this inherited db is a nigthmare. it consists of several related dbs to one main db. now one problem which is evident straight away is that it is quite slow when entering some of the layouts within the main db.

could this be because caluclations are performed from the related dbs and shown in the main db? it is not possible to change the indexing as well, it states that the calculation cannot be stored because the field refernces a related field.

a lot more development work is required and im begininng to think that starting this from scratch i.e. binning the inherited db is going to be easier then understanding why and how the previous developer designed and created this monster!!

any sugestions?

thanks in advance,

ricardo.

[LiveOak]

Stay away from rewriting other peoples files?

I've got one like this (only worse) that I'm working on for a client. Other than trying to get out of doing the job, I'd remove the display of related data from list views whenever possible and consider (gulp!) selected lookups for the really slow stuff (where possible without creating greater problems).

-bd