Query with Sequential Number Field

[Robecca]

Is it possible to create a query with a Sequential Number field?

I have a table where I'd planned to have a primary key field to be an autonumber. However, now I need to delete all records from this table for the current year and then append records for the current year from a query to the table.

I am thinking it is not good for the primary key field to be an autonumber in this senario.

Any suggetions? I have tried dcount, dsum, dmax and nothing is working in the query for a sequential field.

Thank you! Robecca

 

[jdraw]

What are you trying to do in plain English? And why exactly do you think the autonumber is a problem?
Sounds like you have a structure issue.

 

[Robecca]

I have a table that was designed to store last season's bowling average for each bowler on each league they bowl.

However, I now learned that one league does brackets (scratch & handicap) paid out after bowling that evening, but for the handicap bracket it has to use their average as of the previous week. Once they bowl, it refigures their average.

My plan was to append to the season average table the bowler's averages after bowling each week. That way I'd have their previous average.

However, I will also need to delete the entries from the week before and then append the new data.

I have the primary key as an autonumber, when I delete the rows, then append, it gaps. Is that not an issue I should be concerned about in a primary key?

 

[gemma-the-husky]

ideally you would work out the average each time you used it.

if you have to store the average then simply a query something like


update tblbowler set average = newcomputedaverage

you shouldn't need to be deleting/inserting records.

 

[Robecca]

I guess I was having a rough day yesterday, I'd started out with an update query and next thing I know, my brain said I had to do an append query, which then led to a query to delete and obviously my issue with the autonumber when deleting/appending.

Thanks Dave!