Re: More NewEra Conundrums

In article <42q0q3$7t7@cssun.mathcs.emory.edu> sholmes@netcom.com "Scott Holmes" writes: > Hi folks, here's some more NewEra conundrums. I am trying to > retain similar functionality in a NewEra application as I have > in a pre-existing 4GL system. Of question here are "zoom" screens. > When data changes in a specific field (on insert or on update), if > the user has entered a wildcard a new window opens with a pick list. > This pick list also allows the user to enter new selection criteria. > For those of you with Fourgen experience, I'm speaking of their > standard zoom screen behavior. Errr, I only have *very* limited NE experience, but I have seen that the backward 4GL compatability isn't always 100%. I'm not sure you should be approaching the problem in the same way that it was done in 4GL and *especially* not the way FourGen do it. It might be better to re-look at the problem and address it in a totally different way... > I have successfully added a second 4gi (I'm using p-code) to my > application. This new window is opened using a "run 'fglgo peopzm'" > command. I've passed the filter through an intermediate table and the > screen is correctly populated. The user can then select the record > wanted. The intermediate table is updated and the window closed. > Finally, the field in question (people code) and corresponding display > fields (people name fields) are correctly populated. > I'm having two problems, however: 1) For a period of time, when I wished > to start the "zoom" program the system reported a stack error and > everything died. I had to reboot the computer to get it to work again. I had a similar problem and it transpired that it was a bug in my code! <blush> It seems that some coding errors can have pretty dramatic side-effects. > And: 2) When the filter is "1=1" the entire people table is brought > up. My development database contains 8058 records of size 307. It appears > that the memory required to hold these records becomes unavailable after > exiting the zoom program, everything slows down to a crawl at that point. > Is this usual behavior for Windoze systems? Err, well, ummm ... I don't know. What I *do* recommend is that you force deallocation of objects & FREE up as much as possible within the zoom, just to see if it makes any difference. > I'm not a Windoze person and this is my first involvement with > developing anything on DOS/Windows systems. I'm having serious reservations > about the reliability of NewEra applications at least in a Windoze > environment. New Era *is* a new product. However, it doesn't seem to be particularly unstable. What *does* seem to be a problem is that if you get something subtly wrong (which is pretty easy!), the side-effects can be pretty spectacular. > A further question about problem 1; the books tell me > that I can't start up a second NewEra application with a run statement. > One book has a caveat that it is possible but only one program may access > a database. Both of mine do and, aside from the stack error, it seems to > work. Hmm, surely a self-contradictory statement? Possibly what Informix were saying is that if you try to access the database from both programs you'll get a stack error! :-) Spokey the Wheeler------------------------------------------------------------- "Billy Boy" - das aufregende andersche kondom!