Re: CLOSE and FREE

In article 1Cw@cix.compulink.co.uk, onlinedbc@cix.compulink.co.uk ("Malcolm Weallans") writes: >In my humble opinion I think that this has something to do with front-end >and back-end memory allocation. I think CLOSE releases memory in the >front-end but FREE releases memory in the back-end, or it might be the >other way round. > >Malcolm Weallans >Online Database Consultancy >2 Arkley Court >Maidenhead >Berks >SL6 2YR >Phone 0628-72154 >Fax 0628-37463 >CIX - onlinedbc free as used in 4gl or esql/c on a cursor id will free the backend resources associated with that id. close as used in close database frees ALL resources of the backend associated with that front-ends' connection to the database server. free as used in esql/c on a pointer to a sqlda structure frees the front end resources as any free of a pointer would do, it should also free the sqlda resources used in the backend (if any like from the last describe) Karl