microsoft.public.inetserver.asp.db Google Group

Re: website asp db design

2009-12-30T19:48:38Z

Thanks millions for helping and information,

Re: website asp db design

2009-12-27T17:19:22Z

It's good that you're starting off thinking about security, but there's no
point to having a second database that I can see, at least, not for the
reason you are proposing. The user is not (or should not be) directly
logging into the database. It is your server-side code that should be the
only link between the user and the database, thus giving you complete

website asp db design

2009-12-26T23:11:28Z

I would like to use SQL server as my asp website database.
I would like to know that is it a good idea to create 2 databases one
for all the link and the other one fo real database for security
reason.
Since the dynamic website must let user login when user hit the home
page to get url link information, it can avoid security issue if user

Economical Auction Site

2009-12-25T03:58:46Z

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-16T18:32:16Z

I would say I might be an ultraminimalist,...but it would take too long to
say it :-)
P.W.

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-16T17:21:19Z

I have it "live" now and so far it seems to do ok. I use NTFS permissions
to control who can use it rather than try to create a built-in
authentication/useraccounts "thing" with the ASP. I've done that before with
other things in the past,...but I'm gettng lazy.
They'll let me know if they have problems. I'll work on perfecting it with

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T22:06:08Z

Good to hear that your problem is getting resolved.

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T21:26:44Z

Bob Barrows wrote on 15 dec 2009 in microsoft.public.inetserver.as p.db:
Which can effectively be shortened to:
strApproved = NOT strApproved = ""
or for the average minimalist to:
strApproved = strApproved <> ""
or for the extreme minimalist to:
strApproved = strApproved > ""
=============
Some ultraminimalists would even disaprove

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T19:59:21Z

Keeping in mind that booleans are stored as 0 or -1, I'm not sure the
word "on" would be recognized. This will likely work better:
If strApproved = "" then
strApproved =false
else
strApproved =true
end if

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T19:20:55Z

Oh duh! cDate is fine.

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T18:58:54Z

Bob found the bad spot in the code and that is fixed,..I've just got some
other smaller (yet still annoying) issues to iron out. But the pressure is
off with the dupe thing fixed.
Thanks, Neil

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T18:56:40Z

Ok :-)
OK...
OK...
That's what I was kinda attempting with cDate() but I know it needs to be
better than that. I'll work on that later on.
I wish I would have kept a better record of what it did but I didn't. I
just remember both the Insert and the Update queries had problems,...and one
of them complained about a Type Mismatch in one of my attempts.

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T15:51:44Z

Well, that is a good thing to do, but ... I tested the code on my
machine and it definitely generated an error message when I left the
fields blank ... oh, wait! I left out the line I had to add to
initialize the strErrorMsg variable:
strErrorMsg = ""
If If Document.frmNewEntry.txtTitle. Value = ...
Again, you don't have to do it in Access Design View (although it is

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T15:30:18Z

Very good. That fixed the dupes issue. However I tested the error message
part of it by intensionally leaving a field blank,...no error message like
there should have been,....and it posted to the database with the blank
entry instead of canceling the submit. I'm running out of patients with the

Re: Dup entries when creating a new DB entry (ASP Classic with an MDB file)

2009-12-15T14:48:16Z

You don't have to do this in Design view: you can do it via SQL DDL if
you like:
CREATE UNIQUE INDEX IX_Events_Unique
ON tblEvents (fldStartDate ASC, fldTitle ASC)