Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problem with temp indexes
Message
From
09/03/2004 18:07:10
 
 
To
09/03/2004 16:46:22
Larry Long
ProgRes (Programming Resources)
Georgia, United States
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00884583
Message ID:
00884620
Views:
17
Provided you are ready to close all indexes in the new datasession, you can use something similar:
set excl off
use customer

o=createobject('session')
set datasession to o.datasessionid

*-- scoped to new datasession
SET EXCLUSIVE off
SET MULTILOCKS ON


use customer again 
index on ccust_key to temp.idx

*-- set buffering after you create your index
cursorsetprop('buffering',5)

CLOSE INDEXES
use
erase temp.idx

*-- release your new datasession
o=.null.
Hope this helps, may not be what you want...



>Here's a head-scratcher...
>
>set excl off
>use anytable
>cursorsetprop('buffering',5)
>
>o=createobject('session')
>set datasession to o.datasessionid
>use anytable again
>index on anyfield to temp.idx
>
>after working with the table in the private data session I want to delete the temp.idx file.
>
>use
>erase temp.idx
>
>If I close the table in o then try to delete the index file, it says that the file is in use. When I go back to the first session, sure enough, temp.idx has been set there as an active index.
>
>In o, then tried to issue
>
>SET INDEX TO
>use
>erase temp.idx
>
>Now with the buffering set in the first datasession the "set index to" statement does not work.
>
>Any ideas on how to do this without referring back to the first datasession?
>
>TIA,
Thanks,

Stacy



Black Mountain Software, Inc.
Previous
Reply
Map
View

Click here to load this message in the networking platform