Multi-thread?

[Guest Zoltan Gregor]

Hi,

Multi-thread issue.

I have been learning VG with the Evaluation Edition that allows us to test one line only.

I use the VBScript modules intensively to get, insert and change data of a MySQL database.

I use ADODB.Connection and MySQL ODBC 3.51 Driver and I create variables that are used only in a VBScript module.

 

What happens to the variables in a 4-line situation when all the four lines run the same Visual Basic script and creates the same variable names at the same time.

For example, if all the 4 lines calculates the value of a variable named lngCommission. As I understand, the variable name is a reference to an area of the memory and variable names must be different.

 

I read that variable names created by VG modules like $RV[EnteredAmount] are distinguished for each line and there is no confusion. But what about vbscript variables? (How) Can the system guaranty that if I calculate values for vbscript variables at the same time, on different lines, there will be no chaos or system crash?

 

Zoltan

 

P.S. The advise somewhere on this website to use MySQL instead of MS Access was very useful. Access stopped working very often. It has never happened to MySQL; it is very reliable.

[SupportTeam]

I have been learning VG with the Evaluation Edition that allows us to test one line only.

Evaluation version allows you to test with up to 4 lines simultaneously.

What happens to the variables in a 4-line situation when all the four lines run the same Visual Basic script and creates the same variable names at the same time.

The variables are only defined for the line on which they were created.

I read that variable names created by VG modules like $RV[EnteredAmount] are distinguished for each line and there is no confusion. But what about vbscript variables?

VBScript variables only persist during the running of the VBScript - so they would be valid not just per line but only during that particular running of the script as well.

 

VoiceGuide can connect to any Database. Access is OK for simple applications, but MySQL or SQLServer is the choice for more advanced apps.