>>>Hi Dan,
>>>
>>>>On the repost if the variable is the same, we'll get another add because the mode from the previous data is "add". It gets a little confusing.
>>>
>>>If I were browsing a site, clicked add, added a record and clicked back, i would assume that if I clicked add again I would get another record. IMHO, I think the way your describing it to me is the way it should be. Do you have this site up so we could maybe take a look?
>>
>>Actually, I click add, then I click refresh and say "Yes" to "Repost from data?" and that adds another record. I've been telling the other programmer that maybe we should just make this a training issue. "Don't do that."
>
>Is there nothing unique about the data being added that you can't catch it on the server?

The way that drumbeat works is it leaves a hook called BeforeOpen that allows you to place your own code right before the page processes your data requests.

The problem is that it is here that a mode internal to drumbeat that needs to be set prior to drumbeat opening and processing the dataset.

But in order to check the data as you say, to check for duplicates, which is what we did originally, we need to open the table in the beforeOpen function. Unfortunately this was causing some problems with drumbeat.

As an alternative we were looking for ways to use session variables or form variables that we could check when first coming into the page that would let us know we were dealing with a refresh. The pain is dealing with the drumbeat framework.