We will try a simpler approach using the database directly on the MainWindow, instead of creating the database on a separate class.
Then it will be simpler for you to analize the code.
Then we will come and reply with the results![]()
We will try a simpler approach using the database directly on the MainWindow, instead of creating the database on a separate class.
Then it will be simpler for you to analize the code.
Then we will come and reply with the results![]()
Last edited by Wer_Bn; 17th October 2016 at 09:03.
Meanwhile, we found a VERY interesting fact.
We changed the database to the MainWindow class:
- Database and query instance in the MainWindow Class (previously we had a database wrapper class)
- Both variables are initialized in MainWindow Class constructor
- query is being prepared in the contructor, after the database is created and opened
- Upon a button pressed action, we had new entry to the database, through bind and exec. It TOTALLY works. We get as many entries as many times we press the button.
So...
Next step is to check if the use of DLL libraries is jeopardizing all of this. The class that used to have the database and query instances is in this DLL...
Any feedback on this?
Should be no issues with having code in your app exe or the DLL I wouldn't think. That said, I haven't had to use Windows in many years now, so perhaps someone else can chime in.
I write the best type of code possible, code that I want to write, not code that someone tells me to write!
Bookmarks