Thread: Bug reports & Feature requests

This is something that was reported by some other fastIBL users too. It worked ok until a moment when is starting to behave as you mention. Unfortunately, I still work on discovering what might be the problem. This process is complicated by the fact that I did not managed to replicate this problem on one of my computers so that I can study it properly. Basically, the same app. version and the same db were functioning ok if moved to a different computer.
One solution found so far was to use a different fastIBl version. Do you have the latest version taken from the server? Pls. try this first and let me know if it starts working.

Yes it's the last version. I'll try and move db's and app. itself to another comp. Will see if it acts weird there too ;) Thanks for answering.

good luck :)