Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > comp.databases.xbase.codebase > #16

Re: Questions...

Show all headers | View raw

in regards of d4skipND(..)
cbTable->setdeleted=true;  //false ???
will does the same for the  d4skipND(..).

codebase6 has most of the need of clipper/foxpro...
only need to use via C/C++ .

cheers!


On Thursday, 31 July 1997 15:00:00 UTC+8, Brian Dukes  wrote:
> Questions aimed mainly at Sequiter,  but perhaps others may want to add to
> the list!!!
> 
> I've experienced dBase and CA-Clipper (with other RDD's as well) for my
> xBase knowledge and now i'm converting a Clipper app to C++ with codebase
> 6.2,  I notice some fundamentals missing.
> 
> Now I appreciate that *I* have the *FULL* source code to CodeBase, so
> anything that is missing I can code myself for myself;  but some of the
> fundamentals *I* think are missing ought to be in the core product.
> 
> 
> 1. In dBase/Clipper you have a command SET DELETED, which allows you to
>    toggle on or off the ability to SKIP into  DELETED records or to
>    AUTOMATICALLY hide them from you.   This is very handy, and you do not
>    need to have an index with a ".NOT. DELETED()" expression.  For small
>    tables, it is feasible that there may be NO index required.
> 
> 2. A Tag4::KeyCount() & Tag4::KeyPosition() feature would be "real" handy!,
>    this would allow you to correctly draw scroll bars down a list of
>    records;  because you know how many records are there and where you
>    currently are!
> 
> 3. A Tag4::KeyAdd() & Tag4::KeyDrop() feature would allow you to build an
>    index based on "user" selected criteria; You would also need the ability
>    to build an empty tag to do this,  so I guess a Tag4::Clear() type
>    command would also be handy.
> 
> 4. A Tag4::Scope(), Tag4::ScopeTop() & Tag4::ScopeBottom() function set
>    would allow you to scope a portion of a database, so that a Data4::top()
>    would go to the ScopeTop() rather than bof(),  but bof() would be true,
>    because logically ScopeTop() would be the top of the file.
> 
> 5. The ability to extend the expressions that are parsed by the index engine
>    or the query engine for adding user-defined functions to index keys,
>    obviously using a well defined API for developing such functions.
> 
> 6. A Data4::WildSeek() function so you can wild-card match expressions,  if
>    you are interested I have a function which I used in my Clipper
>    applications written in C, that I used to create Wildcard searchs.
> 
> 
> I'm sure others have got more to add to this, it would be interesting to see
> if there is any support from other users for some of the above ideas.  If I
> know Sequiter WILL do them, I can wait.  If I know Sequiter WILL-NOT do
> them, then i'll do them myself at some point.   If I knew Sequiter would
> include MY enhancements in future releases, i'd do them now!
> 
> So folks lets have some input,  lets see some ideas being generated here!!
> 
> Brian.
> -- 
> Brian Dukes - email: bdukes@crox.demon.co.uk
>               http://www.crox.demon.co.uk/cellar/
> 
> Error 1010: Wit error, tagline humour not found

Back to comp.databases.xbase.codebase | Previous | Next | Find similar

Thread

Re: Questions... jameschong@tpg.com.au - 2015-04-09 22:40 -0700

csiph-web