Error message when editing a view: No tables were found. Please check your connection and schema settings.
4 June, 2014
Hi
I get the following error message when trying to edit a view.
No tables were found. Please check your connection and schema settings.
Screenshot attached.
I have never seen this issue before.
Thanks
I get the following error message when trying to edit a view.
No tables were found. Please check your connection and schema settings.
Screenshot attached.
I have never seen this issue before.
Thanks
Hi Hemil,
It looks like the DB schema is not visible using the data source connection details.
If you have not changed the data source connection details, I would check the underlying DB itself.
Can you please check the settings of the data source and let me know your findings.
You may also need to ask around the office if any DB changes have been made.
Please let us know your findings.
Regards,
David
It looks like the DB schema is not visible using the data source connection details.
If you have not changed the data source connection details, I would check the underlying DB itself.
Can you please check the settings of the data source and let me know your findings.
You may also need to ask around the office if any DB changes have been made.
Please let us know your findings.
Regards,
David
David,
Not sure what happened but this seemed like a glitch. It started working fine after a couple of hours without any intervention.
Thanks.
Not sure what happened but this seemed like a glitch. It started working fine after a couple of hours without any intervention.
Thanks.
Hi Hemil,
That is good news!
I'm guessing when you were editing this view, the database tables were not accessible (for one reason or another). Now they're back, so it's all good.
If you see this issue again, just have a quick check to see what has changed and pass on any information you have, or if you have any specific questions to help identify where the issue lies.
Regards,
David
That is good news!
I'm guessing when you were editing this view, the database tables were not accessible (for one reason or another). Now they're back, so it's all good.
If you see this issue again, just have a quick check to see what has changed and pass on any information you have, or if you have any specific questions to help identify where the issue lies.
Regards,
David