Joost van der Sluis wrote:
Well, I put some code in each of the update sql StringLists. I don't guarantee it is completely correct, but it should be close. This did not seem to make any difference. Is this worth a bug report ? In the mean time, as it is probably only a Lazarus designer issue, I will try modifying it in code somehow.When I set ParseSQL to False, the object inspector in Lazarus says "updating is only possible if ParseSQL is true" - unless I make it readonly, which defeats the purpose.That's a but, I think. It should check if there are any update/delete/insert queries provided. If that is the case, you can make a query updateable, even if ParseSQL is false. Re the string length issue, I have changed the application I am working on too much to use it to double check exactly what happened, so I will set up a minimal application and submit a bug report on that once I am sure I wasn't dreaming. I only have the fpc that came with lazarus, and it doesn't look like that. I tried recompiling and reinstalling the SQLDBLaz package with the 'generate debugging info' option checked - it wasn't previously - hoping that that might achieve the same result, but it doesn't seem to have. I am happy to keep playing with this, but any words of wisdom would be appreciated! I am still a bit lost between the packages under lazarus and the stuff under fpc under lazarus, and how they interact.So you have to recompile fcl-db with debug info. If you have the full fpc-sources, go to fpc/packages/fcl-db and execute 'make clean all OPT='-gl' ' After you have done that you have to install the freshly created .ppu's. You could copy them over the old ones yourself. Or you could use 'make install' if the system is configured right. (I have started looking to add some documentation to the wiki area, but this also is a new adventure for me!) cheers, John |
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal