Servoy / Headless Client / MS Access on sqlserver

Classic Servoy
1

Hi All,

We have made small headless client solution on an sqlserver database. The headless solution works fine: it is a simple input screen that adds a record to the database. However The database is part of a Microsoft Access solution that is used to further process the data. When a user tries to change the data in Access it raises an error: another user is changing the record. However if I change the record from the Servoy Solution it works fine. And the problem only arises for the records we added with the headless client, we can still edit/delete the normal / old records.

It looks like a locking problem, but I cannot identify it in Enterprise manager. Anyone an idea what I missing here? We tried all the hard procedures: killing the application server, killing the repository etc.

Thanks,

Gert-Jan Aaftink
NEM bv

2

To answer my own question, as a help to developers that may run into this problem in the future: the problem turned out to be originated in a few MS-Access Yes/No fields. In sqlserver this translated into bit fields. The .jsp page did not fill all of the bitvalues, so the remaining were null. And for MS-Access YesNo fields being null indicate that somebody is editing the same record. Servoy had no problem with the values being null. Setting them non-null solved the problem.

Gert-Jan Aaftink
NEM bv