Guys,



I noticed that this article we published did badly on the site.  One 

comment in particular worried me in the reader feedback section



" An ASPToday Reader writes:       Tuesday

27 November 2001

20:02 CST   

  And ASPToday wonder why they get bagged out by other sites...sheesh.



Ratings:  Useful: 1  Innovative: 1  Informative: 1 

"



Okay, so obviously some people didn't like this article, but really the 

only way we can act on this is ask why you didn't like it?



Why didn't this article hit the mark?  Was it really outdated, in which 

case, how could we update it and what other ASP 3 articles can we do that 

you need now!?  Was it a bad method of doing this, in which case what is a 

good method of doing this?



Please tell me what was wrong about this article.  Would anyone find it 

useful?  I thought so, and the reviewers thought so obviously somewhere we 

are not making the right choices.  



Please email me at vickiep@w...  



Thanks,

Vickie

ASPToday editor

I've posted articles to ASPToday in the past and gotten ragged on for it.

I'll be the first to admit I'm not the world's greatest programmer, and I

still do Classic ASP.  I try and write about stuff that's relevant and

useful to today's devs... but my stuff is far from cutting-edge.  The

article people expressed their less-than-favorable opinion about the article

are obviously upset that it's dated, and not exactly revolutionary.  I

enjoyed it, though...well-written and explained effectively.  The fact that

it's not



To be completely honest, ASPToday shouldn't be surprised that this type of

thing happens...the fact that Wrox makes writing articles an option to the

public (anyone that can write a good ASP article with supporting code)

leaves this open.  Other ASP sites like 4GuysFromRolla.com and ASP101.com

are a bit more selective in who they let publish, and so have more control

over the content and level of complexity of it.  Thus, their content looks

more "advanced" by comparison.



Those type of sites are less consistent with their updating schedule as

well...and ASPToday apparently shoots for 1 new article each weekday.  This

inevitably leads to stories being bashed at one time or another for not

being "acceptable" enough with the crowd.  They can let an article sit as

the lead story for days and days...if it's popular and getting lots of

feedback.



As a journalist, my stance about criticism of one's work is that people can

say what they want, and they always will...you can never make everyone truly

happy...but I get paid either way.   :)





----- Original Message -----

From: "vickie" <vickiep@w...>

To: "ASPToday Discuss" <asptoday_discuss@p...>

Sent: Wednesday, November 28, 2001 9:40 AM

Subject: [asptoday_discuss] Flexible and Reusable Pagination and Navigation

using ASP, JavaScript and ADO (Feedback on this article)





> Guys,

>

> I noticed that this article we published did badly on the site.  One

> comment in particular worried me in the reader feedback section

>

> " An ASPToday Reader writes:       Tuesday

> 27 November 2001

> 20:02 CST

>   And ASPToday wonder why they get bagged out by other sites...sheesh.

>

> Ratings:  Useful: 1  Innovative: 1  Informative: 1

> "

>

> Okay, so obviously some people didn't like this article, but really the

> only way we can act on this is ask why you didn't like it?

>

> Why didn't this article hit the mark?  Was it really outdated, in which

> case, how could we update it and what other ASP 3 articles can we do that

> you need now!?  Was it a bad method of doing this, in which case what is a

> good method of doing this?

>

> Please tell me what was wrong about this article.  Would anyone find it

> useful?  I thought so, and the reviewers thought so obviously somewhere we

> are not making the right choices.

>

> Please email me at vickiep@w...

>

> Thanks,

> Vickie

> ASPToday editor




$subst('Email.Unsub')

> Read the future with ebooks at B&N

>

http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&categoryid

=rn_ebooks

>

Hi Jason



I'm John, the new Technical Editor on ASPToday. I've found your various

posts on this forum to be really useful and informative, thanks.



In your post below you mention the different publishing processes taken by

different websites and I thought it would be useful for you and everyone

else to know the process we use at ASPToday.com. You rightly say that we

'make writing articles an option to the public', but we make sure that only

the best articles get published by following this process:



Article ideas are emailed to us either from existing authors or interested

first timers. We also get ideas from places like this forum and from

programmers who have visited our site and have good ideas that they want to

see made into articles but do not want to write themselves - in these cases

we find authors to write the articles for us. These ideas are reviewed by

Vickie and me and sometimes by external reviewers. If we think it would make

an interesting and informative article, the author will submit a first

draft. This is also reviewed by us and by 2 external reviewers. The article

then gets returned to the author to deal with the comments and suggestions

that have occurred in the reviewing process. If we, or the reviewers, do not

think that the article will be good enough, even after a rewrite by the

author, then we will bin it.



If the article has made it through the review process, then after the author

has rewritten their article, either Vickie or I will edit it to check that

it is still relevant, useful, readable and that all the code works. Only

then will the article be published.



I hope this is helpful for you to know. Any questions please either reply

via this forum or mail me at johnc@w...



Thanks



John



-----Original Message-----

From: Jason Salas [mailto:jason@k...]

Sent: 28 November 2001 12:10

To: ASPToday Discuss

Subject: [asptoday_discuss] Re: Flexible and Reusable Pagination and

Navigation using ASP, JavaScript and ADO (Feedback on this article)





I've posted articles to ASPToday in the past and gotten ragged on for it.

I'll be the first to admit I'm not the world's greatest programmer, and I

still do Classic ASP.  I try and write about stuff that's relevant and

useful to today's devs... but my stuff is far from cutting-edge.  The

article people expressed their less-than-favorable opinion about the article

are obviously upset that it's dated, and not exactly revolutionary.  I

enjoyed it, though...well-written and explained effectively.  The fact that

it's not



To be completely honest, ASPToday shouldn't be surprised that this type of

thing happens...the fact that Wrox makes writing articles an option to the

public (anyone that can write a good ASP article with supporting code)

leaves this open.  Other ASP sites like 4GuysFromRolla.com and ASP101.com

are a bit more selective in who they let publish, and so have more control

over the content and level of complexity of it.  Thus, their content looks

more "advanced" by comparison.



Those type of sites are less consistent with their updating schedule as

well...and ASPToday apparently shoots for 1 new article each weekday.  This

inevitably leads to stories being bashed at one time or another for not

being "acceptable" enough with the crowd.  They can let an article sit as

the lead story for days and days...if it's popular and getting lots of

feedback.



As a journalist, my stance about criticism of one's work is that people can

say what they want, and they always will...you can never make everyone truly

happy...but I get paid either way.   :)





----- Original Message -----

From: "vickie" <vickiep@w...>

To: "ASPToday Discuss" <asptoday_discuss@p...>

Sent: Wednesday, November 28, 2001 9:40 AM

Subject: [asptoday_discuss] Flexible and Reusable Pagination and Navigation

using ASP, JavaScript and ADO (Feedback on this article)





> Guys,

>

> I noticed that this article we published did badly on the site.  One

> comment in particular worried me in the reader feedback section

>

> " An ASPToday Reader writes:       Tuesday

> 27 November 2001

> 20:02 CST

>   And ASPToday wonder why they get bagged out by other sites...sheesh.

>

> Ratings:  Useful: 1  Innovative: 1  Informative: 1

> "

>

> Okay, so obviously some people didn't like this article, but really the

> only way we can act on this is ask why you didn't like it?

>

> Why didn't this article hit the mark?  Was it really outdated, in which

> case, how could we update it and what other ASP 3 articles can we do that

> you need now!?  Was it a bad method of doing this, in which case what is a

> good method of doing this?

>

> Please tell me what was wrong about this article.  Would anyone find it

> useful?  I thought so, and the reviewers thought so obviously somewhere we

> are not making the right choices.

>

> Please email me at vickiep@w...

>

> Thanks,

> Vickie

> ASPToday editor




$subst('Email.Unsub')

> Read the future with ebooks at B&N

>

http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&categoryid

=rn_ebooks

>








$subst('Email.Unsub')

Read the future with ebooks at B&N

http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&categoryid

=rn_ebooks

Hi Vickie;



I read (i.e., skimmed) that article when it first arrived and again in

response to your request below for feedback. I opened the article

because I was interested in the topic. My interest comes from the fact

that I have been working on a project in which navigation is a central

issue. However, the article begins with "motherhood and apple pie"

generalities that are a waste of time to read through and then launches

into various low-level details that do not relate particularly to my

interests. As a result I was not able in a short time to ascertain what

the article was about or whether some coding mechanisms contained

therein might be useful to me. 



As editors, you ought to persuade your writers to explain clearly right

at the top what capabilities they will demonstrate and what techniques

will be used so that readers can easily tell whether for their own

purposes the article should be trashed, filed, or studied.



Lou



-----Original Message-----

From: vickie [mailto:vickiep@w...] 

Sent: Wednesday, November 28, 2001 9:40 AM

To: ASPToday Discuss

Subject: [asptoday_discuss] Flexible and Reusable Pagination and

Navigation using ASP, JavaScript and ADO (Feedback on this article)



Guys,



I noticed that this article we published did badly on the site.  One 

comment in particular worried me in the reader feedback section



" An ASPToday Reader writes:       Tuesday

27 November 2001

20:02 CST   

  And ASPToday wonder why they get bagged out by other sites...sheesh.



Ratings:  Useful: 1  Innovative: 1  Informative: 1 

"



Okay, so obviously some people didn't like this article, but really the 

only way we can act on this is ask why you didn't like it?



Why didn't this article hit the mark?  Was it really outdated, in which 

case, how could we update it and what other ASP 3 articles can we do

that 

you need now!?  Was it a bad method of doing this, in which case what is

a 

good method of doing this?



Please tell me what was wrong about this article.  Would anyone find it 

useful?  I thought so, and the reviewers thought so obviously somewhere

we 

are not making the right choices.  



Please email me at vickiep@w...  



Thanks,

Vickie

ASPToday editor




$subst('Email.Unsub')

Read the future with ebooks at B&N

http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&catego

ryid=rn_ebooks

Hi Lou,



Thanks for your input.  



I think you are really quite right.  We should be making clear at the top 

of articles what this article is about.  This is something we can tighten 

up on and will tighten up on.  Thanks for bringing it to the forefront.



Out of interest, would there be any article that would help you achieve 

your tasks in your current project?



Thanks

Vickie



> Hi Vickie;

> 

> I read (i.e., skimmed) that article when it first arrived and again in

> response to your request below for feedback. I opened the article

> because I was interested in the topic. My interest comes from the fact

> that I have been working on a project in which navigation is a central

> issue. However, the article begins with "motherhood and apple pie"

> generalities that are a waste of time to read through and then launches

> into various low-level details that do not relate particularly to my

> interests. As a result I was not able in a short time to ascertain what

> the article was about or whether some coding mechanisms contained

> therein might be useful to me. 

> 

> As editors, you ought to persuade your writers to explain clearly right

> at the top what capabilities they will demonstrate and what techniques

> will be used so that readers can easily tell whether for their own

> purposes the article should be trashed, filed, or studied.

> 

> Lou

> 

> -----Original Message-----

> From: vickie [mailto:vickiep@w...] 

> Sent: Wednesday, November 28, 2001 9:40 AM

> To: ASPToday Discuss

> Subject: [asptoday_discuss] Flexible and Reusable Pagination and

> Navigation using ASP, JavaScript and ADO (Feedback on this article)

> 

> Guys,

> 

> I noticed that this article we published did badly on the site.  One 

> comment in particular worried me in the reader feedback section

> 

> " An ASPToday Reader writes:       Tuesday

> 27 November 2001

> 20:02 CST   

>   And ASPToday wonder why they get bagged out by other sites...sheesh.

> 

> Ratings:  Useful: 1  Innovative: 1  Informative: 1 

> "

> 

> Okay, so obviously some people didn't like this article, but really the 

> only way we can act on this is ask why you didn't like it?

> 

> Why didn't this article hit the mark?  Was it really outdated, in which 

> case, how could we update it and what other ASP 3 articles can we do

> that 

> you need now!?  Was it a bad method of doing this, in which case what is

> a 

> good method of doing this?

> 

> Please tell me what was wrong about this article.  Would anyone find it 

> useful?  I thought so, and the reviewers thought so obviously somewhere

> we 

> are not making the right choices.  

> 

> Please email me at vickiep@w...  

> 

> Thanks,

> Vickie

> ASPToday editor




> $subst('Email.Unsub')

> Read the future with ebooks at B&N

> http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&catego

> ryid=rn_ebooks

> 

Vickie;



As I mentioned to you in an earlier e-message, I have been working on

conversion of an Access 2000 ADP (i.e., Access Data Project meaning that

it keeps forms and logic in an Access database file but connects to a

SQL Server database for "data") to a Web application based on ASP.NET.

The main challenges that I perceived were keeping page to page

navigation under logic control (solved by using .hta rather than IE

itself), a mechanism whereby each new page would be able to find out

upon activation what route the user took to get there, what argument was

passed, and the values that were in controls of predecessor pages when

each one requested a successor. These problems were all solved in a

manner that I found satisfying. However, for the particular Access ADP

in question, it appears that it will make more sense economically to

make the Access version of the application available via tsweb than to

complete the Web version.



So, I am not looking for any particular help at the moment. However, I

would be interested in marketing the capability that I developed if a

suitable means were available.



Lou Klauder



-----Original Message-----

From: vickie [mailto:vickiep@w...] 

Sent: Wednesday, November 28, 2001 3:35 PM

To: ASPToday Discuss

Subject: [asptoday_discuss] RE: Flexible and Reusable Pagination and

Navigation using ASP, JavaScript and ADO (Feedback on this article)



Hi Lou,



Thanks for your input.  



I think you are really quite right.  We should be making clear at the

top 

of articles what this article is about.  This is something we can

tighten 

up on and will tighten up on.  Thanks for bringing it to the forefront.



Out of interest, would there be any article that would help you achieve 

your tasks in your current project?



Thanks

Vickie



> Hi Vickie;

> 

> I read (i.e., skimmed) that article when it first arrived and again in

> response to your request below for feedback. I opened the article

> because I was interested in the topic. My interest comes from the fact

> that I have been working on a project in which navigation is a central

> issue. However, the article begins with "motherhood and apple pie"

> generalities that are a waste of time to read through and then

launches

> into various low-level details that do not relate particularly to my

> interests. As a result I was not able in a short time to ascertain

what

> the article was about or whether some coding mechanisms contained

> therein might be useful to me. 

> 

> As editors, you ought to persuade your writers to explain clearly

right

> at the top what capabilities they will demonstrate and what techniques

> will be used so that readers can easily tell whether for their own

> purposes the article should be trashed, filed, or studied.

> 

> Lou

> 

> -----Original Message-----

> From: vickie [mailto:vickiep@w...] 

> Sent: Wednesday, November 28, 2001 9:40 AM

> To: ASPToday Discuss

> Subject: [asptoday_discuss] Flexible and Reusable Pagination and

> Navigation using ASP, JavaScript and ADO (Feedback on this article)

> 

> Guys,

> 

> I noticed that this article we published did badly on the site.  One 

> comment in particular worried me in the reader feedback section

> 

> " An ASPToday Reader writes:       Tuesday

> 27 November 2001

> 20:02 CST   

>   And ASPToday wonder why they get bagged out by other sites...sheesh.

> 

> Ratings:  Useful: 1  Innovative: 1  Informative: 1 

> "

> 

> Okay, so obviously some people didn't like this article, but really

the 

> only way we can act on this is ask why you didn't like it?

> 

> Why didn't this article hit the mark?  Was it really outdated, in

which 

> case, how could we update it and what other ASP 3 articles can we do

> that 

> you need now!?  Was it a bad method of doing this, in which case what

is

> a 

> good method of doing this?

> 

> Please tell me what was wrong about this article.  Would anyone find

it 

> useful?  I thought so, and the reviewers thought so obviously

somewhere

> we 

> are not making the right choices.  

> 

> Please email me at vickiep@w...  

> 

> Thanks,

> Vickie

> ASPToday editor




> $subst('Email.Unsub')

> Read the future with ebooks at B&N

>

http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&catego

> ryid=rn_ebooks

> 






$subst('Email.Unsub')

Read the future with ebooks at B&N

http://service.bfast.com/bfast/click?bfmid=2181&sourceid=38934667&catego

ryid=rn_ebooks