Received: from icebox.venux.net (icebox.venux.net [216.120.166.10]) by hub.org (8.10.1/8.10.1) with ESMTP id e8LHOns87416 for ; Thu, 21 Sep 2000 13:24:49 -0400 (EDT) Received: from doot (cx853045-b.phnx1.az.home.com [24.177.75.28]) by icebox.venux.net (Postfix) with SMTP id 7C53C26202; Thu, 21 Sep 2000 13:32:16 -0400 (EDT) Message-ID: <009401c023f1$5561b0d0$0200000a@doot> From: "Mitch Vincent" To: , "Brian C. Doyle" References: <5.0.0.19.2.20000921130926.02c2ad30@pop> Subject: Re: Multiple Index's Date: Thu, 21 Sep 2000 10:28:18 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200009/168 > Hello all, > > How would I prevent a user from submitting information to a table once they > have already done so for that day. The best you could probably do is to go back and delete undesired recoords at the end of the day because if it is as you said, they've already put the information into the database. > I would need them to be able > information on future dates as well as have information in the table from > past dates from that user. Not positive what you mean here but just use a date (or timestamp) column in the table to indicate when the record was added. > I am looking for something like insert user_id, date, info where user_id > and date are not the same... does that make sense? Nope, it doesn't -- at least to me :-) How about some table structures and some more information, I'm just not exactly sure what you'd like to do.. -Mitch