bb.donnay-software.com

Hi, Bruce.

Move all accesses/assignments to the var(s) to a get/set-function which sets the value or returns it. Place your debug code there (use DC_CallStack). Do you work with XPF-files and "RESTORE FROM" / "SAVE TO"? Maybe you restore the value there.

Hi, Fred. The errors you get may have something to do with the fact that the tooltip system runs in a different thread. You don't have access to your workareas there! It's quite hard to display tool tips depending on data in a workarea. Your gets need to set values in get/set-functions or even publi...

We use "Help & Manual" (http://www.ec-software.com/), which is a very comfortable documentation system. It creates any kind of output, a well formatted printable manual and all variants of Windows help files aswell - from the same source. Really good software.

I just compared to builds of my major app, one from today and one from march 1st (28 days). The difference is 3,700 lines of code, no cut & paste (and some code deleted aswell!). That makes about 130 lines a day, weekends counted. And I had a week off inbetween - I finished my 6th novel, and wrote 1...

Hi, Bruce. 1. Use visual styles and manifests. 2. Use ownerdrawing within browses to show cells containing lot more information, icons, mixed contenses and so on. Do it with the "subclass" clause of DCBROWSE. You can do almost everything with this - it's unlimited! (They only thing I didn't get to w...

I use eXpress++ for more than thirteen years now, if I count correctly. I learned a lot about object orientated programming in the meantime (most of it from Roger), I created lots of classes, GUI elements and stuff, improved my database programming and knowledge about codeblock logics, pre-processin...

Hi, Fred. This is a very important concept in Xbase (an other languages aswell). If you transmit a function parameter "normally" (by value), just the value of the parameter is moved to the function. A local copy of this parameter is created by the function. Whatever the function does with this param...

@Brian: Just for your understanding. Opportunistic locking is a mechanism intended for speed improvements, which causes entire files to be cached on the client workstation. It's easy to understand that this will cause problems in file sharing scenarios, as we all have with DBF based applications. Th...

Hi, Brian. What I was trying to say: We don't care for damned oplocks with (30 percent) and without (70 percent) ADS. They simply don't make a difference, and all settings we tried just slowed down everything. In ADS/Server situations, oplocks are not necessary even if they would help without ADS. I...

Our software runs at > 1,000 sites and on more than 5,000 workstations, and we don't care for oplocks at all. We did as Steffen first mentioned this possible solution for data problems (in 2004, as I remember), and we found out that almost didn't make any difference. It just caused trouble, nothing ...