>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>Has VBasic a Macro command like foxpros &.
>Thanks.
No, but you can use the scripting control to execute code on the fly.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
And keep in mind that for many data-centric actions, against, say, an ADO recordset (or even DAO), you can construct strings In other word,s you might reference oRecordSet.fields("LastName") -- and "lastname" can be a variable: oRecordSet.fields(TheFieldIWant).
I'd really recommend re-thinking approaches for VB, where it is possible (and it isn't always!), because using the scripting component to execute code on the fly loses the benefit of early binding. It's sort of like using some of the fox 2.x approaches in VFP -- sometimes it's necessary, but as soon as you start macro-expanding aliases, etc., you should be asking yourself if there is a better way, more in line with the language.
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. - Bertrand Russell
