Buffering

[blkm74]

I am developing a application that will run on a NT LAN (Foxpro and DBF). The buffering is good for a LAN or use SQL to insert, update and delete records?
which is stable?

 

[Mike Gagnon]

When an application is well designed buffering works quite well. We have an application used by 25 users over LAN and WAN and I used optimistic buffering mode on most tables and once we got all the little kinks out it runs very well.

 

[blkm74]

Thank you for your comments.

I want to know which buffering is better, optimistic or pessimistic?

My database is foxpro's DBC, buffering is suitable for it?

Thanks!

 

[Mike Gagnon]

Yes buffering is suitable for it. The buffering is normally set in the dataenvironment of the form (Although you can also set the buffering by code every time you open the table). If you create a form and add tables to the dataenvironment, you can then set the buffering mode you need. Buffering is almost a must in a multi-user environment, it allows everyone to work on the same tables without getting conflicts. As to the best buffering level...that is up to you or the client to determine. Use the help file and read up on "Buffering data", it will list the different "levels" of buffering available. I normally use "5", which means the record is only locked when the user presses the TABLEUPDATE button.

 

[danceman]

I agree with mgagnon, there is good advice there. like he said read up on buffering. also look at tableupdate, tablerevert, curval, oldval. Attitude is Everything