Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Private Data Session, what set commands does they need?
Message
 
To
19/02/2003 16:09:01
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00755183
Message ID:
00755227
Views:
11
Hi Claude,

FWIW, here's the one I use. Notice it's a regular .prg file, because that way it sets the current data environment. If it were a class, it would set the environment that was active when the class was instantiated.
* Program....: SETPRIVATEDATASESSIONENVIRONMENT.PRG
* Version....: 1.0
* Author.....: Andrew Coates
* Date.......: March 27, 1999
* Notice.....: Copyright © 1999 Civil Solutions, All Rights Reserved.
*            : Released into the public domain Febuary 20, 2003
*            : Code supplied AS-IS -- No warranty expressed or implied
* Compiler...: Visual FoxPro 06.00.8167.00 for Windows
* Abstract...: Sets the environment for a private data session - called from a program because it operates in the data session from which it was called
* 	as opposed to method code which operates in the data session of its parent object
* Changes....:

* List of commands taken from the SET DATASESSION help topic
SET ANSI OFF
SET AUTOSAVE ON
SET CARRY OFF
SET COLLATE TO "MACHINE"
SET CONFIRM OFF
SET DELETED ON
SET EXACT OFF
SET EXCLUSIVE OFF
SET FIELDS OFF
SET FIXED OFF
SET LOCK OFF
SET MEMOWIDTH to 50
SET MULTILOCKS ON
SET NEAR OFF
SET NULL OFF
SET REPROCESS TO AUTOMATIC
SET SAFETY ON
SET SECONDS ON
SET SYSFORMATS ON
SET TALK OFF
SET UNIQUE OFF
Cheers,

Andrew

>I am working on a application that uses private data sessions. I found that set commands are not honored and have to be put in the init method of the data enenviorment of the form.
>
>Can some one either tell me what set commands need to be in the init method or point me to the list. So far I found that I need set century on and set reprocess to commands.
>
>TIA


If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?


From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."


All my FoxTalk and other articles are available on my web site.


Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform