Hiya all...

I have been watching this thread and you (Venelina) hit an interesting point - many consultants of the 'hardware' industry never look at the software running on their machines - and thus cause many problems for the client. On the same token, you come in and identify a serious flaw in the software design - and then you have to justify it. I had a similar problem when I walked into 'consulting' on someone elses system - they were running a really thin client over a very 'average' LAN - the result was all of the screen calls and .prgs were killing the LAN. Solution (in this case) = fatter client. It was much easier and heaps cheaper. And like you, I had to, umm, 'certify' that this would help by way of my experience.

By definition a database is a storage device - not a 'usage' device :: just like you don't keep all of the folders in your filing cabinet on your desk :: you surely don't keep tables of a DBC open when not in use.

>"my experience show that you will become crazy."
>:-)
>Thats what I'm already feeling about this problem.
>(not that i'm much of a "normal" person now :-D )
>
>This warnning I sent you, because as consultatnt I was hired from bulgarian company, which have problems with crashes of IS. They by advise of software developers changed server, swithces, UPS almost everything. when I revised system found that they keep opened in memory 174 DBFs sometimes memory overloading and ...
>When I explain where is the problem guys ask me:
>Do you know how difficult is to develop that kind of system mem?
>This force me to show them all my certificates of Database Profesionalist.
>Explaining that I know, but may be they don't know. :-)