I'm fairly new to MySQL and have a strange issue that I hope someone can assist me with:
One of our company websites has four types of users(admin, agent, processor and enrollee); the processor inputs the enrollee profile information via the front-end of our site and the info is stored within our MySQL database. Normally after this happens, our admins, agents and processors are all able to view the new enrollee info on the front-end of the site.
At the beginning of the year (Jan 2, 2013), any new enrollee info that was normally entered by our processors are now not showing up on the front-end at all. It's strange because all of our previous entries (prior to Jan 2, 2013) are still able to be viewed/edited via the front-end, so it's just happening to all new entries after Jan 2, 2013.
Each enrollee entered has it's own id number that is auto-generated in the database for every new entry created. With this in mind, our accounts populate on the front-end as such:
With the '150' example being the new entry unique id. Our front-end website still shows entries UP TO number 248, but right at 249 (ex: websitename.com/admin/admin_enrollments.php?id=249), I receive an error stating:
Error in query:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 31
So, I check the syntax within the code and it shows as:
$premiumInfo = enrollmentForms::getPremiumInfoByID($enrollment['planRef_id'],$enrollment['planName'],$enrollment['premiumMode']);
To my limited knowledge, all looks good - and this command still works perfectly with all entries BEFORE id 249, so I'm stumped as to why the entries have just decided to stop showing up on the front-end. The SQL database shows all new entries being populated within the back-end tables just fine, but they are just not showing up on the front end for some reason.
In addition, 100% of the files within the website have remained unedited/untouched for over three months, and every other category is showing and populating just fine, so this is really boggling my mind as to where the issue could be. Also, our processors upload PDFs simultaneously while entering enrollee info, and I noticed that the PDF the processor uploaded at the moment the site stopped populating new enrollees was the largest one ever uploaded (at araound 5MB: not too large, but largest one ever uploaded), so I think maybe there was a server timeout, error, or something out-of-the-ordinary that could have lent to there being a break, error or something that I can't figure out.
We've tried contacting the original developer to no avail, so I'm stumped as to what I should do or where I should go to find the appropriate assistance would be greatly appreciated.
I'm mostly a front-end developer, and have limited knowledge in back-end SQL knowledge, so that's where I'm coming from. If any other relevant information is needed to access the above scenario, I can provide; Thanks in advance for any help.