There are two ways to handle the X's in a spreadsheet...
1. Enter them in separate columns like A1 = 200, B1 = 12, A2 = 199, B2 = 13, and then have sort the sheet on score first, then X's... for printed results you can concatenate the two columns into one cell. I generally do that on other sheets - one for the match results that the shooters want to see, and one for the results for the NRA
2. Enter the score first, then the X's as a decimal i.e. 200.012, 199.013, and that way everything sorts naturally.
The 'problem' per se with a spreadsheet is that a lot of manual fiddling is typically involved in terms of adjusting the info in this cell, adjusting the number of rows for how many shooters you have in each class, drag-n-copy formulae into the new cells, pulling shooter info from another page (assuming you retain info for regular attendees), making sure that the *right* persons info gets linked to the right row, sorting individual sections of a sheet by class, etc.
All of which can, and has been done. Spreadsheets are wonderfully flexible tools, even if you *never* get into any kind of scripting (programming). But you are essentially pounding a square peg through a round hole: Hit it hard enough and it will go through (unrelated trivia: that *is* essentially how a dowel plate works for making custom wooden pegs) but that does not make it the right tool for the job. The barrier to entry for spreadsheets is so low (Excel is pervasive, and if you don't like M$ software, there are several good options with similar feature sets, from Libre/Open Office to Google Sheets)
About 99% of the above would be massively easier with a relational database - including data validation to (at least partially) idiot proof the data entry... but the front end (user interface) becomes a problem. RSTAT uses MySQL (typically free) for the back end database, so in theory someone with the right coding chops could come along and write a new front-end to tie to it...
