>that title should have been 'creating' not opening.. but hey.
>
>I have a system which runs many jobs, these jobs are all old standalone prg's, I made the part of my system that runs the prg's have it's own private datasession, I thought that this would hide and protect all the systems database and tables from the code lurking in the old prg's, however a few use create() and the new tables are by default inserted into my open database even though that database is not in the current datasession, I wasn't expecting that behaviour. without going through all the old prgs and adding FREE to the creates can I hide my database away? again, I thought that would have been done with the new datasession thing.
Try CREATE CURSOR instead of CREATE TABLE.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
