Search results for query: *

Sorry guys for delay. I was on holiday. Thanks for your suggestions about INSERT INTO.. and AV. I check all this. I modified the AV settings to avoid the folders with the data. Yes, the INSERT INTO is ok. The problem persists all the same. I have mapped out the cleanest and fasted way to go...

With all the information given, let me try to reach the bottom of the problem. Thanks a lot. You have helped much in the area and I appreciate.

Would you by any chance be knowing another possibility of what the problem could be?

Sorry I didn't phrase my self properly. My intention is to update those tables using other means as I figure out what to do. Currently they are updated directly at the client machine so the Os has to write the changes back to the server. I think it is this scenario that is causing the...

Olaf, I ain't displaying the data in any way. I don't use any control for this tables. I USE the table in code then only look for a record. That's all. Can the OS in this case 'think' that my table has changed when I close it? Thanks alot for your patience. Benson

Olaf, Sorry to bother you again. If the files are only read but never written to, is there a chance, from your experience, that they could get corrupted? I have particular tables and they are big, their CDXes easily get corrupted and need reindexing. I have other means to update them if user...

Olaf, If that is the case then no need to try let me explore other options. Thanks alot. Benson

Hi, The IT manager made the registry entries as Smb1 and Smb2. From Microsoft I have SMB1 and SMB2. Are these keys case-sensitive?

Olaf, I appreciate your input. I will consider your suggestions Thanks a lot. Benson

Olaf, I think I missed that - enabling SMB1. Is it too late to use the ALASKA MSI now, you think? If I add the SMB1 will that suffice? Do I need to do it in all workstations afresh? Thanks for you patience. Benson

Olaf, No. SMB2 only. I guess this was not okay? Thanks for your input.

Olaf, Sorry. It's here: http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html Thanks

Olaf, The server was restarted yes. The key to change was missing so we added the same as per instructions. Thanks Benson

Griff, Yes. I use the normal vfp command window to browse the records. The bad characters I noticed I wrote some code to clear them from the fields. Thanks Benson

Olaf, Yes they did a restart on the workstations. msi: No. The registry was edited manually. Thanks for your input. Benson

Griff, The IT manager has a team of staff who helped her. >> structural indexes Yes the app is using CDXes all through. >> particularly long keys & large number of indentical keys Not quite but to be honest I don't know how long this would need to be to cause issues >>spoilt records I removed...

Hi Friends, They did everything as advised but the problem persists. I stayed at the hospital the whole night and the few users who on duty did not complain about anything till morning. They posted transactions and everything was very ok. By the time I was leaving in the morning nothing wrong...

I will definitely post back!

Thanks Griff. That's exactly what I am going to do. Thanks so much. Benson

Griff, I have been having the thought to try your suggestion but I have not come accross some info on the pros and the cons. Will data corruption be avoided in this case? If the data is first opened on the server as you suggest? I want to try that, seriously. Do you have any info on what...