Thank you all for such awesome (and timely) advice. I got my script to work, so I'm glad I posted the question. I have only just recently returned to Python scripting so I'm in the process of relearning the syntax. Obviously I need to learn a few things...even simple things, like the difference between single and double quotes, the combinations of these, and when to use them. A couple of these responses have also opened up other options and approaches to solving the same problem...something of which I really appreciate.
I'm going to put all of these responses into my "How 2" folder for future reference for sure.
I'm scheduled to take the first ESRI Python course in February, on the 20th, with plans to take the more advanced course in probably June if possible. I might as well really sink my teeth into this as the benefits are HUGE when it comes to geoprocessing for sure (and much more).
I delved into arcpy in August-September as I needed to write a script that would automate a process from FME data conversion to Portal for ArcGIS publishing. I got it to work entirely in December, but then I ran into problems. The file geodatabase to which FME adds the converted AIS data has grown to be very cumbersome...it is now over 100-million points and I have only completed data from January to August (the plan is to convert data for each year). However, before it's uploaded to Portal I filter it using the MOD option to select 1 in 10 records...so the final file size is much more manageable (I'm thinking that I should perhaps get FME to do this before it adds to the GDB too).
What I'm planning to do is every 4 months (using the Select script you helped me fix) select the previous 3 months of AIS data and then dump those records into a Q1, Q2 etc. file geodatabase, which will keep the main file geodatabase at a much more management size. With over 100-million points my script currently takes over 40 hours to run, but it's only 3-4 hours if it's 3-4 months worth of data (the script will just run after midnight on the first of each month).
The final data in Portal is then used to create heat maps where our Operations Department can then analyze to see where ship traffic is mostly concentrated in and around our harbor.
Thank you very much again