kensheehimura1
Programmer
good day,
im creating a com+ application, a client/server application,using visual basic 6, with 2 library or project , named BOShoeLib, And DOShoeLib which consist of several components on it, when coding on class on BOShoeLib and creating instance of the components in DOShoeLib i use the CreateObject Keyword, but when im going to access components in the same library, BOShoelib, for Example when im coding in the BOShoelib Project, and create an instance of an object withing thesame project i use new
Example:
1. BOShoelib to DOShoelib
dim doCustomer as DOShoelib.Customer
set doCustomer = createobject("DOShoelib.Customer"
2. BOShoeLib to BOShoelib
dim boCustomerReg as BOShoelib.CustomerReg
set boCustomerReg = new BOShoelib.CustomerReg
is the second item correct? or do i have to use Createobject instead of new? which is better? thanks,
GOD BLESS....
im creating a com+ application, a client/server application,using visual basic 6, with 2 library or project , named BOShoeLib, And DOShoeLib which consist of several components on it, when coding on class on BOShoeLib and creating instance of the components in DOShoeLib i use the CreateObject Keyword, but when im going to access components in the same library, BOShoelib, for Example when im coding in the BOShoelib Project, and create an instance of an object withing thesame project i use new
Example:
1. BOShoelib to DOShoelib
dim doCustomer as DOShoelib.Customer
set doCustomer = createobject("DOShoelib.Customer"
2. BOShoeLib to BOShoelib
dim boCustomerReg as BOShoelib.CustomerReg
set boCustomerReg = new BOShoelib.CustomerReg
is the second item correct? or do i have to use Createobject instead of new? which is better? thanks,
GOD BLESS....