Subscriptions

Hi,

I'm working on a site that requries a subscription. I have ruled out storing CC details in a database so that means that either a user pays for several months at once and then has to manually make another payment when the time is up or else an independent payment company holds on to the details. Perhaps the bank could do this?

Anyone know anything about these latter ideas?

Cheers, WT.

There are companies like PayPal out there that could do your processing for you. Microsoft's Visual Web Developer Express has a starter kit for a PayPal eCommerce site.

http://msdn.microsoft.com/vstudio/express/vwd/starterkit/default.aspx#paypal

Hope that helps

Craist
If the site is small, I suggest using a third party Merchant Account and/or PayPal. Like you said, storing CC details in your own database is not a good idee unless you have major security and I think it's not legal unless the CC Company approuve.
But do these companies hold on to the CC details so that the customer can automatically be charged each month?
Yes they do

Substring

Hello

I have the following string:

myName = "John Smith Curtis"

I want to get the first word, i.e. "John", which means I want to get everything from the start to the first space.

I know I should use Substring but I don't know what to do to remove the first word.

Thanks,
Miguelstring myName = "John Smith Curtis";
myName = myName.Substring( 0, myName.IndexOf( " " ) );

The best way to go though would be to do

myName.Split(" ")(0) -> That will return the first element before the space

If you really want to us substring then do

myName.Substring(0,4)

myName.Remove(myName.IndexOf(' ')) will return "John"

try the following ( i didnt check for going out of bound to keep the example simple)

string myName = "John Smith Curtis";

//get the index of the frist space
int index = myName.IndexOf(" ");

//get the first word
string firstname = myName.Substring(0, index);

//remove the first word
myName = myName.Remove(0, index + 1);

Suggested means to cope with commas etc.

G'day,
In a typical 'contact us' type page what is a recommended way to ensure a message text box gets dealt with properly rather than break at comma's etc.

Is it as simple as using server.encodeHTML() on every passed variable? When I do this I still seem to have problems.

GeoffWhy would you break at commas? I don't get the problem.
Sorry. Error was happening when writing a record of the email to a database.

So if I can change my question...

Is there a best-practice' approach to handling commas etc. when writing to database eg:..."insert into myTable message = '" & server.encodeHTML(msg.text) & "'" is the sort of thing that was breaking if a comma existed in the textbox called msg?

Thanks,

Geoff
The commas should not mess it up within the quotes.

If an apostrophe appears within the string ('), then it will close the string and this is what will mess it up.

The best practice is to use Parameters. These will take care of all these issues as well as protect you against SQL injection and a few other problems you may not have noticed yet.

Survey: What do you name your User table?

Most of the sites that I build have to deal with security at some
point, and this means that somewhere in the database there needs to be
a list of Users.

The naming convention that I (and most everybody I've ever worked with
that cares about such things) use dictates that a table should be named
according to what it contains, and that this name should be singular.
So, Customer, User, Entry are all good, while Customers, Users, Entries
are not so good. Thus, nobody has to deal with Junior Dev Jimmy's
magic ID generation code that occasionally tries to bind a column to
"EntrieID".

The issue I keep running into is that "User" is essentially a reserved
word in ASP.NET, being a property of Page. Thus, I can't use it as the
ClassName for my DataObject that wraps the User table. Thus, I
probably shouldn't be naming the table "User", since every other
DataObject always is named after the table it represents.

I've tried going with "Login" to describe users, but this usually
crashes into somebody's Login.aspx Page object, and besides it's not
quite descriptive enough for my tastes.

That leaves us with "Users" (thus breaking our naming convention),
"tblUser" "UserTable" or "UserRecord" (which all look silly on the
url), "Individual" or "Dude" (which I've actually gone with in the
past).

I'm curious what other people have come up with to attack this problem.
I'm sure I'm not the only one running into it. Let me know what you
think!

Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/because tables are sets, i (like the sqlserver dev group) always make them
pural, so my users table name is Users. in your case UserInfo is probably a
good name.

-- bruce (sqlwork.com)

"jasonkester" <jasonkester@.gmail.com> wrote in message
news:1125699677.612465.206070@.g43g2000cwa.googlegr oups.com...
> Most of the sites that I build have to deal with security at some
> point, and this means that somewhere in the database there needs to be
> a list of Users.
> The naming convention that I (and most everybody I've ever worked with
> that cares about such things) use dictates that a table should be named
> according to what it contains, and that this name should be singular.
> So, Customer, User, Entry are all good, while Customers, Users, Entries
> are not so good. Thus, nobody has to deal with Junior Dev Jimmy's
> magic ID generation code that occasionally tries to bind a column to
> "EntrieID".
> The issue I keep running into is that "User" is essentially a reserved
> word in ASP.NET, being a property of Page. Thus, I can't use it as the
> ClassName for my DataObject that wraps the User table. Thus, I
> probably shouldn't be naming the table "User", since every other
> DataObject always is named after the table it represents.
> I've tried going with "Login" to describe users, but this usually
> crashes into somebody's Login.aspx Page object, and besides it's not
> quite descriptive enough for my tastes.
> That leaves us with "Users" (thus breaking our naming convention),
> "tblUser" "UserTable" or "UserRecord" (which all look silly on the
> url), "Individual" or "Dude" (which I've actually gone with in the
> past).
> I'm curious what other people have come up with to attack this problem.
> I'm sure I'm not the only one running into it. Let me know what you
> think!
>
> Jason Kester
> Expat Software Consulting Services
> http://www.expatsoftware.com/
UserProfile, UserRegistrationInfo, RegisteredUsers, UserCredentials...

Johm

Survey: What do you name your User table?

Most of the sites that I build have to deal with security at some
point, and this means that somewhere in the database there needs to be
a list of Users.
The naming convention that I (and most everybody I've ever worked with
that cares about such things) use dictates that a table should be named
according to what it contains, and that this name should be singular.
So, Customer, User, Entry are all good, while Customers, Users, Entries
are not so good. Thus, nobody has to deal with Junior Dev Jimmy's
magic ID generation code that occasionally tries to bind a column to
"EntrieID".
The issue I keep running into is that "User" is essentially a reserved
word in ASP.NET, being a property of Page. Thus, I can't use it as the
ClassName for my DataObject that wraps the User table. Thus, I
probably shouldn't be naming the table "User", since every other
DataObject always is named after the table it represents.
I've tried going with "Login" to describe users, but this usually
crashes into somebody's Login.aspx Page object, and besides it's not
quite descriptive enough for my tastes.
That leaves us with "Users" (thus breaking our naming convention),
"tblUser" "UserTable" or "UserRecord" (which all look silly on the
url), "Individual" or "Dude" (which I've actually gone with in the
past).
I'm curious what other people have come up with to attack this problem.
I'm sure I'm not the only one running into it. Let me know what you
think!
Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/because tables are sets, i (like the sqlserver dev group) always make them
pural, so my users table name is Users. in your case UserInfo is probably a
good name.
-- bruce (sqlwork.com)
"jasonkester" <jasonkester@.gmail.com> wrote in message
news:1125699677.612465.206070@.g43g2000cwa.googlegroups.com...
> Most of the sites that I build have to deal with security at some
> point, and this means that somewhere in the database there needs to be
> a list of Users.
> The naming convention that I (and most everybody I've ever worked with
> that cares about such things) use dictates that a table should be named
> according to what it contains, and that this name should be singular.
> So, Customer, User, Entry are all good, while Customers, Users, Entries
> are not so good. Thus, nobody has to deal with Junior Dev Jimmy's
> magic ID generation code that occasionally tries to bind a column to
> "EntrieID".
> The issue I keep running into is that "User" is essentially a reserved
> word in ASP.NET, being a property of Page. Thus, I can't use it as the
> ClassName for my DataObject that wraps the User table. Thus, I
> probably shouldn't be naming the table "User", since every other
> DataObject always is named after the table it represents.
> I've tried going with "Login" to describe users, but this usually
> crashes into somebody's Login.aspx Page object, and besides it's not
> quite descriptive enough for my tastes.
> That leaves us with "Users" (thus breaking our naming convention),
> "tblUser" "UserTable" or "UserRecord" (which all look silly on the
> url), "Individual" or "Dude" (which I've actually gone with in the
> past).
> I'm curious what other people have come up with to attack this problem.
> I'm sure I'm not the only one running into it. Let me know what you
> think!
>
> Jason Kester
> Expat Software Consulting Services
> http://www.expatsoftware.com/
>
UserProfile, UserRegistrationInfo, RegisteredUsers, UserCredentials...
Johm