TIP: Click on subject to list as thread! ANSI
echo: pascal
to: KIM FORWOOD
from: PETER BARLEY
date: 1998-04-13 13:09:00
subject: Re: Hmm..

Hi Kim Forwood, hope you are having a nice day
11-Apr-98 04:07:39, Kim Forwood wrote to Peter Barley
                    Subject: Re: Hmm..
 KF> Peter Barley wrote:
 PB>> I am writing a program where the user needs to be able to select
 PB>> options which are appropriate to themselves. but the sysop will
 PB>> be selecting the options that they want to have available (add
 PB>> new ones, remove old ones etc).
 PB>> I want to some how store the information on which users have
 PB>> selected a certain option, but I also need to store another
 PB>> variable (longint) about the user for each of the options that
 PB>> they are slecting.
 PB>> can someone please help me out on how to do this..
 KF> You haven't really explained what you want to do clearly enough
 KF> for any of us to give much assistance. For starters, how/where do
 KF> you need to store this data? Where is this data taken from, and
 KF> how is it being stored there (byte, integer, strinng, record of
 KF> some sort)? And how is storing the other information (the longint)
 KF> pertinent to your problem (why did you mention it)?
Sorry that was my fault, I was having a bad day, my monitor had just
blown up earlier, and one of my programs had crashed because I used a
integer instead of a longint (thats why I mentioned it). Erm. Im not
particularly bothered HOW it is stored but I was thinking of 2 files of
records, but if there is a better way then that would be better.
Basically the structues Im looking at are like this (these might change
as the program improves etc).
Type UserFile : Record
        UniqueID  : longint;
        FirstName : string[20];
        SurName   : string[25];
        Fidonet   : String[];     {<= ***** Suggestions of length please}
        Crash     : Boolean;
     end;
Type SourceFile : Record
        UniqueID  : Longint;
        Name      : string[50];
        Location  : string[80];
      Description : string[80];
        Dateadded : Longint;     {}
        Active    : Boolean;
        Kill      : Boolean;
        Accesses  : Longint;
     End;
So that is the basis of the information used by the program stored, but
then from that I need another record somewhere saying that :
The person with UniqueID 1, is connected to Sourcefile.UniqueID 1, and
they have set it to activate every 7 days.
So I need someway of saying which sourcefile.uniqueID's the user is
connected to (Which can be as many as they like), and for eash of these
connections I need a Activate every x days value, and a value for the
last access. So you would kinda of have a record like this :
Type ConnectFile : Record;
        Userfile.UniqueID   : Longint;
        Sourcefile.UniqueID : Longint;
        Activate            : Longint;
        Last_activated      : Longint;
     End;
So basically what Im asking is what is the best way of doing this? is it
to have a separate file of each user containing the infomation on
connections, a separate file for each sourcefile containing the
information on connected users, or a big file that somehow stores all
users with connections to all sourcefiles? (If the later, then would I
have to user a separate record for every sourcefile that the user was
connected to??)
If you want to know anymore then please just ask (replys may take a bit,
as Im off back to university soon, so replys will take place when I
visit home).
 KF> Kim Forwood
On another note, in another message to me U said you send Trep 1.0 to
www.download.com, well I couldnt find it, so can you tell me where else
it is available from. Or is it possible for you to email me it at
university?
-=> Yours sincerely, Peter Barley <=-
--- Terminate 5.00/Pro http://tdcff.home.ml.org
---------------
* Origin: Freeware? : Netmail To:Infomail Subj:Twodogs @ (2:2502/666.15)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.