Detect current workspace? 3

[Paco75]

Hi,

I want to know if there is a way to detect the current workspace. I need it to save the current workspace and DBF() on entering a .prg and then restore them before exit that same .prg

Ex:

SELECT 1
USE aTable EXCLUSIVE 
DO prg_program WITH aParameter

&& get the workspace (should return 1 here)
[COLOR=red]oldWorkspace = ???????????????[/color]
oldTable = DBF()

SELECT 2
USE another Table EXCLUSIVE
&& ... do something ...

SELECT oldWorkspace
USE oldTable

thanks

 

[GriffMG]

OldWorkSpace = Select(0)

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Paco75]

Thanks!

 

[Mike Lewis]

Paco75,

In your code, you have this line:

SELECT oldWorkspace

You will need to change it as follows:

SELECT (oldWorkspace)

You probably already knew that, but I thought I'd mention it.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy

 

[Paco75]

Yes i knew it. but thanks.

Also in the solution (for others that might seek to do the same) i use ISEXCLUSIVE(oldTable) to save if the table was open in EXCLUSIVE mode... otherwise i open it in SHARED.

 

[Olaf Doschke]

If you need your table untouched and selected when coming back from a called routine, don't just remember the workarea, you also need to check if your table is still open in it. Therefore it's even better to also remember the alias via ALIAS() and reselect that and check if your're in the same workarea.

May be a bit overcautious, depending on the routine you call.
You might even start a new datasession before starting something messing up with your session:

lnCurrentSession = Set("Datasession")
o = CreateObject("Session")
Set Datasession To o.DatasessionID
* Call routine
Set Datasession To lnCurrentSession

If the routine should work on your data that's of course not the way to go.

And also, if you call a method of an object, that will run in the datasession the object is created in.

Ok, enough said. Maybe I'm more confusing than helping, but keep it in the back of your mind, you can also control datasessions, not only via forms with private datasession.

Bye, Olaf.

 

[TamarGranor]

Paco - one other comment. You have SELECT 1 in your code. It's a bad idea to rely on specific work areas. Instead of:

SELECT 1
USE aTable EXCLUSIVE

use:

SELECT 0
USE aTable EXCLUSIVE

That will open the table in the first available work area. From there on out, you refer to it by alias, not work area, like this:

SELECT aTable
* Now do something with aTable

In fact, you rarely need to actually select a work area. Most commands accept an IN clause and it's good practice to use it wherever it's available.

Tamar

 

[Paco75]

Your are right Tamar! Thanks for the tip!