Search found 211 matches
- Tue Dec 09, 2025 2:43 pm
- Forum: Chit-Chat
- Topic: Windows 11 working like W10
- Replies: 15
- Views: 20839
Re: Windows 11 working like W10
As I purchased a new notebook which of course comes with W11 I installed ExplorerPatch. I had to install a beta version (from 4 days ago); the 'regular' version did not work. But it does not allow me to place the taskbar to the right
You do not have that issue?
Hi Dick,
I use in W11 OpenShell ...
- Tue Dec 09, 2025 1:31 pm
- Forum: VO & Vulcan
- Topic: Olewebbrowser exception despite errorhandler
- Replies: 5
- Views: 516
Re: Olewebbrowser exception despite errorhandler
Hi Dick,
blast from the past: if E_OUTOFMEMORY is returned, Try to fiddle with the ?etProcessWorkingSetSiz??? memory functions, old IE had the tendency to gobble up Processmemory and not to free it. Back then (XP Win7 days) forcing to minimze the IE Window triggered a cleanup of ...
blast from the past: if E_OUTOFMEMORY is returned, Try to fiddle with the ?etProcessWorkingSetSiz??? memory functions, old IE had the tendency to gobble up Processmemory and not to free it. Back then (XP Win7 days) forcing to minimze the IE Window triggered a cleanup of ...
- Wed Sep 24, 2025 6:55 pm
- Forum: Visual FoxPro
- Topic: Execscript support, Runtime compilation or razor templates?
- Replies: 10
- Views: 15723
Re: Execscript support, Runtime compilation or razor templates?
Brian,
I have posted my take on missing "base vfp DNA" in other thread here in vfp forum.
Perhaps you should offer a prioritized list of features xSharp must support for your programs.
regards
thomas
I have posted my take on missing "base vfp DNA" in other thread here in vfp forum.
Perhaps you should offer a prioritized list of features xSharp must support for your programs.
regards
thomas
- Wed Sep 24, 2025 6:46 pm
- Forum: Visual FoxPro
- Topic: Chances for some small optimizations of vfp runtime?
- Replies: 8
- Views: 33788
Re: Chances for some small optimizations of vfp runtime?
Kevin,
my guess is xSharp implementation was started without detailed analysis which vfp features would be needed for how large a percentage of current vfp apps. More a kind of "Which syntax do we need to support, so that VO programs can be built with Vfp syntax" and not "How and why are vfp ...
my guess is xSharp implementation was started without detailed analysis which vfp features would be needed for how large a percentage of current vfp apps. More a kind of "Which syntax do we need to support, so that VO programs can be built with Vfp syntax" and not "How and why are vfp ...
- Wed Aug 20, 2025 12:59 pm
- Forum: Visual FoxPro
- Topic: Chances for some small optimizations of vfp runtime?
- Replies: 8
- Views: 33788
Re: Chances for some small optimizations of vfp runtime?
Hi Chris,
but I think you believe that using the NeedsAccessToLocals ... so probably is not something to really worry about.
Mostly correct, I thought that before the call local would be collected and then injected - but viewed that as "time between calling line, wanted Macro expansion and ...
but I think you believe that using the NeedsAccessToLocals ... so probably is not something to really worry about.
Mostly correct, I thought that before the call local would be collected and then injected - but viewed that as "time between calling line, wanted Macro expansion and ...
- Wed Aug 20, 2025 10:23 am
- Forum: Visual FoxPro
- Topic: Chances for some small optimizations of vfp runtime?
- Replies: 8
- Views: 33788
Re: Chances for some small optimizations of vfp runtime?
Hi Robert,
thx for the detailed explanation - esp. last paragraph - makes clear, how xSharp handles 1st parameter array modification or creation in the cases like aDir, aFields or aMembers, where an existing array is modified (even when called without @ on calling source line) or created inside the ...
thx for the detailed explanation - esp. last paragraph - makes clear, how xSharp handles 1st parameter array modification or creation in the cases like aDir, aFields or aMembers, where an existing array is modified (even when called without @ on calling source line) or created inside the ...
- Mon Aug 18, 2025 2:12 pm
- Forum: Visual FoxPro
- Topic: Chances for some small optimizations of vfp runtime?
- Replies: 8
- Views: 33788
Chances for some small optimizations of vfp runtime?
Hi Robert, Chris & Fabrice,
I read a bit in the sources, trying to get my footing back in Dotnet and xSharp.
a) If I am not mistaken, the code for the vfp "evaluate()" is in
/Runtime/XSharp.RT/Functions/Macro.Prg
as it has the NeedsAccessToLocals(TRUE) qualifier Robert mentioned when discussing non ...
I read a bit in the sources, trying to get my footing back in Dotnet and xSharp.
a) If I am not mistaken, the code for the vfp "evaluate()" is in
/Runtime/XSharp.RT/Functions/Macro.Prg
as it has the NeedsAccessToLocals(TRUE) qualifier Robert mentioned when discussing non ...
- Sat Aug 16, 2025 1:56 pm
- Forum: Chit-Chat
- Topic: vfpodbc.dll / DBMigration by fish
- Replies: 3
- Views: 8443
Re: vfpodbc.dll / DBMigration by fish
Hi Karl,
From Vfp POV VfpODBC is old - not venerable, but out of time, as it only supports up to vfp6, no Autoincrement, no index BINARY and so on. If it works for your dbf structure, fine. Then I'd reinstall it (several ways listed on VfpX, with files for runtimes or standalone).
Differences in ...
From Vfp POV VfpODBC is old - not venerable, but out of time, as it only supports up to vfp6, no Autoincrement, no index BINARY and so on. If it works for your dbf structure, fine. Then I'd reinstall it (several ways listed on VfpX, with files for runtimes or standalone).
Differences in ...
- Sat Aug 02, 2025 7:22 am
- Forum: Visual FoxPro
- Topic: Foxtools functions
- Replies: 3
- Views: 7098
Re: Foxtools functions
As you mention yourself to be rusty in vfp:
AFAIR RegFN tries to register into the DOS 16 bit runtimes, the 32 bit equivalent was called RegFN32. It was used to call into Fll/Dll created by 16 or 32 bit compiler especially for Vfp3 or found on the DOS or NT based OS, as MS allowed via "thunking" to ...
AFAIR RegFN tries to register into the DOS 16 bit runtimes, the 32 bit equivalent was called RegFN32. It was used to call into Fll/Dll created by 16 or 32 bit compiler especially for Vfp3 or found on the DOS or NT based OS, as MS allowed via "thunking" to ...
- Sat Apr 12, 2025 6:46 pm
- Forum: Visual FoxPro
- Topic: ADO.NET is probably the best solution for data processing in X# as of today.
- Replies: 1
- Views: 4572
Re: ADO.NET is probably the best solution for data processing in X# as of today.
Hi Xinje,
you are absolutely correct. The vfp programs I still see make heavy use of buffering - the whole context of GetNextModified(), Get/SetFieldState() TableUpdate(), TableRevert() is/was the special sauce in vfp, as it caches part of the (nowadays remote server) tables as Selects on the local ...
you are absolutely correct. The vfp programs I still see make heavy use of buffering - the whole context of GetNextModified(), Get/SetFieldState() TableUpdate(), TableRevert() is/was the special sauce in vfp, as it caches part of the (nowadays remote server) tables as Selects on the local ...

