-=> Quoting Chris Hoppman to Scott Adams <=-

 SA>         In modern machines with gighz machines and such it
 SA>         really isn't that much unless your doing a data hog
 SA>         like a Database program.  But a rule of thumb basically
 SA>         anything is better with pointers.  The main benefit is
 SA>         data storage of course but speed helps.
 SA>         So it depends on how many records you might be dealing with.
 SA>         A few hundred who cares.  A million then yeah use pointers. :)

 CH> How, about 2-10 records at a time.  The program is okay when one user
 CH> is on  the bbs, but when a second or third user is on the bbs then it
 CH> is all hell  tring to type something in the telnet client.  The keys
 CH> seem like they stick. (Wait a few seconds, before they get printted to
 CH> the screen).

     IF only 2-10 then nah pointers not mandatory.  But if your running
     say a million records and USE 2-10 at a time then reding with
     pointers might help.  
        
 CH> The ansi screens scrolls about 3 lines then pauses then scrolls two
 CH> more then  pauses then scrolls 5 more (not in that order, but in
 CH> general it does that). When two users are online.  It sucks and I am
 CH> looking to resolve the issue of  cpu usage then maybe speed up the
 CH> program. 

     OH ...I see...a multi-user board yes definitely needs timeslices.





... Sinclair - "Your `noble citizens' have stolen credit chips."
--- Fringe BBS