Hi Bob, Since Qbase is essentially untested, other than my own efforts, this is not really surprising.
Would it be possible to send me a copy of the database? It would greatly help with debugging to have access to a database that makes the system crash. Rgds, Daniel On Sun, Sep 10, 2017 at 1:07 PM, Bob Spelten via Ql-Users < firstname.lastname@example.org> wrote: > Op Sat, 09 Sep 2017 15:06:06 +0200 schreef Daniel Baum via Ql-Users < > email@example.com>: > > Hi all, >> >> Latest pictures. >> >> Qbase is now rescalable. It starts at 512x256: >> >> https://www.dropbox.com/s/exexw4s5ppexyi4/qbaseTab512x256.jpg?dl=0 >> >> and can get as big as you want: >> >> https://www.dropbox.com/s/o9yi56lqms4ppg3/qbaseTabBig.jpg?dl=0 >> >> These pictures show the automatic proportional column width in the tabular >> view, which has actually always worked, but was less than obvious until >> now. >> >> Getting there... >> >> Looking good. > > I played with the current version as found in BP143 and I did get a Qlib > error when hitting the Tabulate button. > I must admit it was a big database of over 3000 records and 6 fields, with > one of 500 characters. > Qbase probably tried to get them all in one array for the menu items. > The big field could of course be cut to the visible column width. > > "Qlib error 16, array too big" suggests there are too many elements. > A dimensions check would be nice here, so the Tab action can be aborted > with a warning, before the program crashes. > (See sections 6.4 & 8.8 of the Qlib 3.3 manual) > > Bob > > -- > The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/" > _______________________________________________ > QL-Users Mailing List > _______________________________________________ QL-Users Mailing List