![]() ![]() However, that is very inconvenient for those of us that have to work with multiple databases whose schemas have different names. The ONLY thing that works with any measurable success is explicitly specifying the schema name in the query. confirming that the connection is not read-only.toggling auto-commit and transaction modes.Steps to repeat: run a query, try to edit a field in the results, experience error message, search online for a resolution, trudge through the forums here to see if anybody has fixed it yet, repeat.Īll of the tips and workarounds found here and elsewhere (e.g. Unresolved table reference." Even the simplest of queries will experience the problem. The grid editor for result sets has an intermittent problem where it will not allow the editing of a field unless the schema name is explicitly referenced in the query. This has been an on-going problem for years and it still is not resolved as of version 2021.2.3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |