I will pay someone to help me write this code! It's easy!

<i><b>Originally posted by : Tony O (tony2468@aol.com)</b></i><br />Listen, i need this scripting done badly. If someone will help me write, or write it for me, i will pay them for it! I'm desperate here! Email me!<br /><br />I need a fairly simple .asp script that updates the website on its own. The page /members911/index2.asp has 4 links on it. They are: Story 1, Story 2, Story 3, Story 4. I need an .asp script (preferably one that is on the actual page, rather than an include, that does the following:<br /><br />Every Mon-Friday (NOT saturday or sunday), the page needs to increment the filename by 1. In other words, right now, the story 1 link is (for monday) /members911/stories/FF/0117.asp. On Tuesday, that link needs to become /0118.asp. On wednesday, it needs to be /0119.asp, etc. Friday is the last increment of the week, and then on sunday at midnight (mon. morn) it starts again. The files are already on the server. The number really and truly is the only thing that needs to change. Here's the catch... I want there to be a cookie set on their computer, such that if they access the site on monday, they get monday's content. But if they don't hotsync again until like thurs, they get tuesday's content. That way, they never miss a day, and the content updates when they are ready to update it. Each time they reload, it brings them closer and closer to the absolute most current set of content. So if they reload more times on thurs, for example, it brings them up to thursday's stories. You follow what i mean? So it gets kinda complicated, but im sure that you guys can do something like this fairly quickly. from the limited .asp i have learned, and the coding ive done before, it doesnt seem like it'd be too hard to write this code. But that's why i need an estimate. <br /><br />Next, i need a member preferences page that lets them choose between 1 of 5 types of stories.<br />1) Pref 1<br />2) Pref 2<br />3) Pref 3<br />4) Pref 4<br />5) Default (one of each)<br /><br />Their choice needs to set a cookie on their computer, just like how the username and password does, that remembers their story preference, and each time they hotsync, we read the cookie, and they will get an index of content, based on their choice. So, for example, if they choose the pref 1 content type, they will get /members911/index_pref1.asp. That index file will look just like index2.asp does now, except that instead of each link being to a different story directory, the link will be to just the directory of their preference. So, the links will look like this...<br /><br />Story 1 (/members911/pref1/0004.asp)<br />Story 2 (/members911/pref2/0003.asp)<br />Story 3 (/members911/pref3/0002.asp)<br />Story 4 (/members911/pref4/0001.asp)<br /><br />That will be on the first day of the week. The next weekday, story 4 will link to 0002.asp, and story 1 will become story 0005.asp. In other words, the current story 1 gets pushed out of circulation, 1 day at a time. It moves from story 1 to story 4, and each day, the next numerical value of story 1 is sent down. Ok, that's it. I hope this is all clear enough.