Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Stop SP's from firing
Message
From
11/09/2006 10:03:51
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
10/09/2006 20:51:53
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01152618
Message ID:
01152748
Views:
25
>>Thanks Hilmar, It probably wouldn't be a bad enhancement to have Global Maintenance switch setting in VFP i.e. disable RI, Triggers and field default values etc, it would save a bit of coding.
>
>Perhaps, but I know of no such option. An alternative RI such as TaxRI - plus your own use of variables for your own stored procedures - is the closest you can get, AFAIK.

Actually, it can be done with the code generated by GenDbc, if it's properly chopped. You can remove all the RI by issuing a series of DbSetProp() calls and Append Procedures From {empty prg here}, running your appends, then reissuing the DbSetProp() calls and Append Procedures from {the krt file extracted by GenDbc} when you're done. It's a PITA of a job to get right, and may actually need a bit of a generator to do right, if you have too many tables. And you better have a good backup in case something gets screwed.

update: actually you don't have to do the procedures part. If you blank all the trigger settings, the procedures would simply not be called.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Reply
Map
View

Click here to load this message in the networking platform