[SOLVED] Editable grid does not work in production environment

Scriptcase 7 Bugs
#1

I’ve created a form as an editable grid. It works great in dev but as soon as it’s published to production I get the error: “An error occurred while connecting to the database”. I’ve checked the db connections on the app and it is the same in dev as in production. I tested this issue by creating a table with 2 columns and built an editable grid form off of that table. I ran it in dev and inserted 2 records. I then deployed it and got the error I mentioned above. It’s pointless to have apps that only work in dev and not production.

edit: This happens with editable grid and editable grid view. We had deployed other apps of this type before SC7 and they work in Prod just fine. No new editable grids are able to be deployed.

#2

Check your connections in dev and production again. And check the data connections with a another tool (by example: Adminer).

#3

I’ve checked it several times and everything is correct. I even cleaned up my project and mass edited the connection to the production connection, generated it all, and deployed it. I have an app that uses 3 apps. A form with a link to the troubled editable grid form and a grid. The grid and form deploy and work fine. The link to the editable grid gives me the error. I put the trouble app on the menu by itself so I could run it without using a link and I still get the same error. I’ve tried creating new apps of all kinds and deploy them and I get the error. What ever update that came out the other day messed up deployment. All the apps I created before the update work in production. Again, any new apps created will not work in production.

#4

Update:
When deploying the apps I made before the update you are prompted for the connection. There are only two connections on the project. The dev db and the prod db. When I deploy the app created after the update some other connection from another project is showing. Where is it coming from? I looked at the connections and It doesn’t exist in the project I’m deploying. What could be causing it to pick up connections from other projects? Why do all newly made apps add this connection at deployment? We have never deployed anything under the connection it’s bringing in by itself.

#5

I think, you’ve perhaps the same problem as I just … I have made ​​a fresh deploy from a testapp and should create two connections for that. A form was not ok, because no connection to the database.

For me it was so, that I have included below Programming/Libraries a tools-library from another project with reference to a connection to that other project …

I have the tools removed and now my testapp only requires one connection and everything ist ok :).

#6

There was a log scheme that another employee created and the project was defaulting to it. I changed the log scheme and everything works fine now. I apologize for the confusion. Please remove this post from bugs.