has service pack2 impact on buffering?

[Nifrabar]

I have on a portable harddisk VFP9 installed so I can use it everywhere.
I recently refreshed my laptop with a fresh win7 installation.
Meanwhile I reinstalled vfp9 with servicepack 2. I never used servicepack 2 before.

Now it happens that with servicepack 2 it seems that buddering is different as without servicepack2. But maybe it's just a setting?

Does this make sense?

-Bart

 

[TamarGranor]

I'm guessing that by "buddering," you mean "buffering." If so, no, there are no changes in SP2.

What are you seeing?

Tamar

 

[Nifrabar]

Hi Tamar,
Sorry for late reply.Oops, buddering..is typo; keys f and d just site by site..

What happens:

I use buffered data on form1.
In form2 (datasession set to 1) I use the buffered data (using SET SQLBUFFERING ON)
and proces some data.
After closing form 2:

In my VFP app on portable disk I see directly the changes
In my VFP app on laptop with servicepack2 I have to skip a record forward and back (in fact that forces a save-record).

So what is going on?

Any suggestion?

TIA
-Bart

 

[Olaf Doschke]

Are the settings the same on both computers?

What do you mean with app on portable disk? If you compare VFP9 withou SP and wih SP2 I'd assume you do so on two different computers. Have you compared all settings?

IOf you need a record skip forth and back the difference might be REFRESH seetting or something in that area.

Working with SQLBUFFERING ON just means form2 or any code working on the same buffered alias would select data from the buffer of it instead of disc. with SQLBUFFERING OFF sql will always only read from dbf file, so buffered changes are invisible.

But that's not turning buffering on, it just specifies to read from the buffer, if it's used. And also it does not refesh a browse or grid on another form when working with buffering. A grid only refreshes on SET REFRESH settings and if you issue grid.refresh() or form.refresh(). The automatic refresh you can set by SET REFRESH can happen instantly or take a while, that may make you see what you saw, but just by coincidence and if repeated would perhaps yield another result. Also if your new installation has set refresh to -1 or 0 you'll never see changes without refreshing through moving within the grid or something else refreshing the grid.

Bye, Olaf.

 

[Nifrabar]

Hi OLaf,
I do have a VFP9 installation on a portable harddisk.
Also on my portable harddisk are my projects.
So I can run/develop using every machine I plug in this portable HD.
Using the VFP EXE with my app from portable HD works as expected.

I reinstalled my laptop(win7) together with vfp9.
Than I ran my app from the VFP-version on laptop with result as described earlier.

So both VFP-exe's are using same prg's (still not built but under development)

Can I affect set refresh others than afrom within an app or command prompt?

-Bart

 

[Olaf Doschke]

You can affect all setting in tools options and then set as default.
So settings can have different default settings. table refresh interval in the data tab corresponds to SET REFRESH nSeconds for example.

Bye, Olaf.

 

[Nifrabar]

Olaf,
I double-checked all settings. No difference found.
Than I deinstalled VFP with servicepack.
Reinstalled but now without service pack 2 and it works again as a charme...
So the mistery remains.
Maybe there is an undocumented feature in VFP9 I make use of which has been removed with servicepack2 ;-)

-Bart

 

[Olaf Doschke]

Ok,

there is another difference on running VFP installed on a PC than running from an installation done on a portable drive, not on that PC: registry entries are missing, file extensions are not registered.

If you want a fair comparison you need a normal installation with and without sp2.

I nevertheless would use and recomend sp2 in general. If you're having better experience without sp than noone can convince you.

Besides, SQLBuffering has got me several issues and I avoid it, it's nothing you need, vfp worked until without it until vfp9, you only need it, if doing sql on buffered data, not for buffering in general.

You might try your code again with SET SQLBUFFERING OFF and see if that makes any difference.

To turn on buffering for the aliases you still need to either set the form property Buffermode, which actually makes you choose about the locking mode only, or cursorsetprop("Buffering",...) which makes you choose optimistic/pessimistic locking AND row or table buffering.

Bye, Olaf.

 

[Nifrabar]

Olaf,
So I ran my app with fresh VFP > good result
installed sp2 > no good result.

With sp2:
On my form2 I do have the [set sqlbuffering on] in the init.
If set sql turned into off: my form2 is not able to handle the data anylonger.

I will investigate what happens with my data en come back wit results (which might take some time).

-Bart

 

[Nifrabar]

I promised Olaf to revert with my results:
It was hard to find why same programs failed with VFP9 SP2 while those did what was expected with VFP SP1.
At long last I have made some changes to my code to get it to work.
In short:
On my form1 I do data input/change.(buffered)
From form1 I instanciate form2. Here I do some properties in seperate table but based on buffered data of form1.
Finished on form2 > back to form1.
I made changes visible by having a rowsource in a listbox using the SQL solution.
Before I used parametrized view.

So still don't know why failure happened but solved now.
Anyway, again thanks for your time on this subject.

-Bart

 

[Olaf Doschke]

>So I ran my app with fresh VFP > good result
>installed sp2 > no good result.

Did you recompile? You compile with a certain runtime level for a certain runtime level, if you don't recompile all things can happen running SP0 code with SP2 runtime.

Bye, Olaf.

 

[Nifrabar]

well, here you might have a point!
I will pickup a recent BU to see if I can recompile all and observe that result.
-Bart