Thanks Matt. I was able to get things to work by deleting the field under edit/details view. I spotted that the field was listed twice (and confirmed they were indeed the same field). New problem, and not sure if it’s related to what you replied with, if I click edit and save my log file is kicking back an MYSQL error. it looks as if the custom table isn’t being added to the query. I am seeing “=NULL” within the log file error and it happens at the very first field of the custom table.
Cool, everything now works. FYI I wasn’t sure if the problematic field needed to be commented out (my first approach) or the actual file deleted. Commenting out the field in the appropriate cache folder worked however repairing/fixing the site created the problem again (/cache/modules/SPS01_Poolsites/MyMODULENAMEvardefs.php). I located the field within the location you pointed out but simply commenting out the lines of code didn’t work so i deleted the file all together (/custom/Extension/modules/MyMODULENAME/Ext/Vardefs/MyFIELDNAME.php). Another thing worth mentioning for others stumbling upon this post is that the problematic field was not deleted from Studio but simply removed from the Detail/Edit views.