|
From: Olaf K. <ola...@sa...> - 2016-05-12 15:48:50
|
Hello, after we updated the fb odbc driver to 2.04 we have some problems. The frontend is ms access, the tables are linked to firebird and one adodb-connection (every time closed) calls stored procedures. Now, after we call a sp access gets not in every time the new records (the sp inserts for example one), only after the formular is closes (or the entire access), the records will be shown. The old driver 2.00.150 (rc2) works better and faster but since fb 3 I get an error during linking to the tables. Are the tables already linked it works fine. One problem more: We insert in Access a new record in the main-table, after this we go in the ufo (position-table) and everythin is fine, in the second table the reference (year and number) to the main-entry will set. But if we call an stored procedure which inserts this record (special function) and after this we klick to a new record, the given ID (number) is wrong (ID from the insert of the stored procedure). After we klick a second time in the formular, the right number will be shown and the error is not present. The ID will generated with a generator (trigger) in firebird. Thanks for helping. Best regards. Olaf |
|
From: Dimitry S. <sd...@ib...> - 2016-05-12 15:55:55
|
12.05.2016 17:48, Olaf Kluge wrote: > Now, after we call a sp access gets not in every time the new records (the sp inserts for > example one), only after the formular is closes (or the entire access), the records will > be shown. This is obviously a problem with Access transactions handling. -- WBR, SD. |
|
From: Olaf K. <ola...@sa...> - 2016-05-12 16:30:07
|
Hello , I was just wondering why it works with the old 2.00.150 driver nearly perfect and with the new so bad. What can I do? The Access should wait until the record is in the table, with the earlier version this works.. 12.05.2016 17:48, Olaf Kluge wrote: > Now, after we call a sp access gets not in every time the new records > (the sp inserts for example one), only after the formular is closes > (or the entire access), the records will be shown. This is obviously a problem with Access transactions handling. -- WBR, SD. ---------------------------------------------------------------------------- -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Olaf K. <ola...@sa...> - 2016-05-12 16:35:34
|
.. and why works it sometimes and otherwhile not :( -----Ursprüngliche Nachricht----- Von: Olaf Kluge [mailto:ola...@sa...] Gesendet: Donnerstag, 12. Mai 2016 18:30 An: fir...@li... Betreff: Re: [Firebird-odbc-devel] ODBC-Problems Hello , I was just wondering why it works with the old 2.00.150 driver nearly perfect and with the new so bad. What can I do? The Access should wait until the record is in the table, with the earlier version this works.. 12.05.2016 17:48, Olaf Kluge wrote: > Now, after we call a sp access gets not in every time the new records > (the sp inserts for example one), only after the formular is closes > (or the entire access), the records will be shown. This is obviously a problem with Access transactions handling. -- WBR, SD. ---------------------------------------------------------------------------- -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel ---------------------------------------------------------------------------- -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Firebird-odbc-devel mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel |
|
From: Robert M. <ro...@ch...> - 2016-05-12 20:58:19
|
Hi I only sue ODBC to connect Crystal reports and I don't use access but it occurs to me the issue is likely to be that the process takes longer in FB 3 and the access (periodically) silently times out. So you call your SQL / Stored procedure it takes longer than x seconds so access just gives up and steps to the next line of code, however the SQL is still running in FB and later completes. I would look for timeout settings and check your SQLs execute within them. Cheers Rob On 13/05/2016 4:35 a.m., Olaf Kluge wrote: > .. and why works it sometimes and otherwhile not :( > > > > -----Ursprüngliche Nachricht----- > Von: Olaf Kluge [mailto:ola...@sa...] > Gesendet: Donnerstag, 12. Mai 2016 18:30 > An: fir...@li... > Betreff: Re: [Firebird-odbc-devel] ODBC-Problems > > Hello , > > I was just wondering why it works with the old 2.00.150 driver nearly > perfect and with the new so bad. What can I do? The Access should wait until > the record is in the table, with the earlier version this works.. > > 12.05.2016 17:48, Olaf Kluge wrote: >> Now, after we call a sp access gets not in every time the new records >> (the sp inserts for example one), only after the formular is closes >> (or the entire access), the records will be shown. > This is obviously a problem with Access transactions handling. > |