To add more information...

The save is done ok. As soon as the save is done (the SQLExec() update SQL), I can see that the table on disk is having the proper data. But, it is the application that cannot see it ok for a while. If I do several requests following the save, some of them will see it ok, others won't see the updated changes, and then it starts seeing it again. This doesn't make any sense at all. If I do a local SQL, there is no problem. During that timeframe, doing a local SQL will access the data ok from the disk. But, doing it with SPT will produce extremely irritating behavior. Here is a scenario which best describes the weird behavior:

1. SQLExec() does an insert by the use of a regular SQL insert syntax
2. If I look on the disk, the data is well saved
3. The application queries to get the updated data by the use of SPT. Lets say that I do about 20 hits by doing the same transaction which should return a list. In all those 20 hits, sometimes the list does contain the new added record, sometimes not. It may see the new added record for 4 hits, not on the 5th hit and then again starting from the 6th hit. It just goes on and off like that for about 2 minutes. Then, after about two minutes, the application can continue to do the same query and I will see the new added record 100% of the time.
4. During that same timeframe, if I do a local SQL, I will always get the proper data. So, there is definitely something wrong with the way I use the SQLExec() syntax.