Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
BIG BUG: first use noupdate put all next use to read-onl
Message
From
14/01/2004 12:15:21
Mike Yearwood
Toronto, Ontario, Canada
 
 
To
14/01/2004 12:09:48
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00865913
Message ID:
00866813
Views:
32
SNIP
>
>>Am I wrong that the tables can be updated if opened in a private datasession after they were opened in the initial datasession noupdate? If not, it seems we'd be able to further control the unplanned updates, by planning them to occur in a private datasession.
>
>I've tried that several messages upstream from this, and yes, the status of the first use of a table is inherited in subsequent "use again"s only as long as you're in the same datasession. So if we keep the lookups readonly in forms where they're used as lookups, and open them readwrite in forms where they are edited, they will be readonly most of the time - and safe from occasional inadvertent updates.

Interesting.
Previous
Reply
Map
View

Click here to load this message in the networking platform