FiveTech Software tech support forums

... open", }, ; { "Recent ODBC connections", }, ; { "Recent ODBC connections strings", }, ; { "Sets", }, ; { "Workareas", } ; } ) it is from FiveDBU.EXE. what does it mean :?: FWAddLanguage() how does it work :?:

Though SET DELETED ON/OFF is a global setting effecting all WorkAreas, it is still possible to do what you want. There are several ways. I will be posting a few samples soon. Please wait.

... more than one record in the same workarea. If we want to modify more than one record in the same dbf, we need to open the same dbf in different workareas This is not difficult. I successfully used transaction tracking with DBFs.

... this - several instances are opened. To test this, I opened the opendbf-test.exe several times. Each program opens the database 2000 times in 2000 workareas. There are 10,000 open workareas in total. Access via the Internet remains as fast as ever. I think it will remain the same if you consume ...

... only ONE virtual machine for ALL requests. It is built using "multi-threading" so it can attend lots of customers but they ALL share the workareas, the public variables, the global symbol table, etc. This can be very "weak" for security reasons and messy to be properly coded: ...

... create a new method OrdSetFocus() that works like you want but using OrdScope() to accomplish this. Note that you don't need to use any aliases or workareas with database objects. That is all handled automatically by the object.

... ) // where fieldname is an actual fieldname. Does that work? Also try: MsgInfo(oDBF:nArea) Note that TDatabase creates it's own unique workareas which is not going to be 9 in this case. With database objects you never deal with workareas. Your error message: Error description: Error ...

... have taken old code and reduced the number of lines by more than 50% using OOP. I could go on and on and on... Oh, and you never have to deal with workareas again! Tim Stone is using OOP with ADO so he may jump in with some relevant comments.

... as a variable of the invoice class. Note also that the database objects handle finding and using a unique workarea so you never have to deal with workareas again. oInvoice:= TInvoice():new(cInvoice:ID) MsgInfo( oInvoice:oCustomer:name ) To do this the invoice object opens a copy of the oCustomers ...

... ? You can use all options of the database when it is an object. One of the great things when you use an object is that you don't have to deal with workareas at all. You can even have multiple copies of the same database open at the same time, even in the function. This allows you to open a database ...

You can also avoid these kinds of problems by using database objects. Every database object creates its own unique workarea and handles it internally. Thus you never have to deal with workareas.

There is no need to switch workareas.
XBrowse has nothing to do with currently selected workarea.

If you still have any problem, please provide a small sample.

Yes, I'm using different workareas. But the browses are dinamically created so I can't use any alias, I need that the current workarea is the one of the browse with the focus.

Can it be done?

EMG

I assume you are using different workareas for different browses. We can not use same workarea in different xbrowses. Switching the xbrowses does not switch workareas (does not change the selected workarea). XBrowse is also not affected by ...

... built into the database object. oCustomer:Name Is actually a buffer that contains a copy of the data in the NAME field. Also you never need to use workareas or aliases with database objects. Here is an example of how to build a database object for a customer database: CLASS TCustomers from TDatabase  ...