Update Records

Hello -

I have a couple questions I hope that you can help me with. I have an asp page that is retrieving a bunch of records from an Access Database based on a field value (in my case its based on Department). They are then placed in a table format in the asp page. The user can then modify one or many records. Everything was working fine and then we upgraded our IIS Service from IIS5 to IIS6. Once we did that I started getting errors. I was able to update certain departments and not others. This told me the code was good and that the database permissions etc were good. It has to do specifically with the value or similar. I looked further and came to realize that it appears there were to many records to update. The Departments with a few records updated fine. THe ones with 500-1000 were erroring out. I went into the database and deleted the records from 1000 to 500 and everything works.

Does anyone know if there is a record limit to update?

Is there a function on ASP that I can use like Me.Dirty that will search first for updates and then just update the single record?

Is this a result of IIS6?


Here is a bit of my code: This is the area that it is bombing out on....I am not an expert and believe I might have hit an ARRAY size limit. Does that make sense?

Is there an ARRAY size limit?

THanks in Advance

It's like deja vu all over again!

"Don't crosspost in multiple forums, you'll find doing so greatly lessens your chances for a good response."

Why is that.....I dont know if this is a VB issue or an Access issue. If I place the Question in VB and its an Access how do I know it will be seen by the right people?

Yea relax Grumpy Old Man......he just asking a question...

You can address the situation or what ever bug in in your A$$ with a little more decency. WHat are you a Nazi Forum Guard

Mate - you don't need to post it three times. The mods on here are great - if they think it's in the wrong forum, they'll move it to the best place to make sure it gets the best exposure

And you, newb, show some respect!

I could say "because I told you so" but I won't

The main reason is that it's a waste of everyone's time, and replies get fragmented. Personally, I tend to ignore crossposters, but after I spend 10 minutes researching and composing a reply only to find out someone else did the same reply in a crosspost I have the desire to do something more than simply ignoring.

So if you keep up crossposting I'll be happy to add you to my *plonk file