Originally posted by: Greg
Well done. Thanks!
ReplyOriginally posted by: hsmin
Suddenly I came to use ADOX and found this article very useful. Thanks for the work here.
But I'm not familiar with VB syntax so I'll be very glad if you add some VC++ samples.
Keep up the good work.
ReplyOriginally posted by: oblyvion
Shouldn't these articles be proof read before they are "published?" I realize that there are a lot of foreign workers with in-depth knowledge on some of these topics, but that doesn't give them the right to make a shambles of the English language. For example:
"it looks like DAO is splitted to 3 parts..."
"If provider doesn't support property which you want to set value, error will occur."
"if you try to set property for existing object error will occurred when you..."
"You can create them and add into collection or remove."
"and you need to tell to compiler what you do want exactly."
"And don't forget to release objects when you don't need them more."
"Connection string in this case must point to not existing file."
"...you have to reassign its objects to other user or delete them at all."
"...providers do not support this methods."
"You can see that Catalog object do not have properties same as DAO..."
"You can read about it some other articles."
"When Procedure object property Command is
called from program used this provider,
it returns E_NOINTERFACE error..."
"As far as my system do not supports User object,..."
"I cannot force to work it as described in MSDN "
" But realization of Users and Groups collections in ADOX 2.6 possible has bugs."
"If there is no error collection is not empty and vise versa."
"You can use them but if you do mistake and parameters of object will conflict with parameters that you specify..."
"Relation from not unique column to not unique one is a nonsense."
"As far as English is not my native language, excuse me for ugly language strustures."
(You're tellin' me.)
I'm going to stop now because this is just ridiculous! This is certainly not an exhaustive list of all the errors. I can't believe anyone read this over and thought it was worthy of public consumption. Please learn the language. You're an embarrassment to yourself.
bIt is acceptable too If you can explain some problem with body signsb&b Your deep knowledge of the English will not guarantee you a better job in programming community. Try to find your interest in school district forumsb&
ReplybIt is acceptable too If you can explain some problem with body signsb&b Your deep knowledge of the English will not guarantee you a better job in programming community. Try to find your interest in school district forumsb&Reply
you're an embarrassment to yourself. programmation is language independent. if you can read C code you can probably also read Vb Code. I doubt you even understood what was said in that article. if you can do better, then be constuctive and do it. personnally, this article was life saver on many topic of the ADO and I give 5 star to the one who wrote it.
ReplyPersonally, I found this article very useful dispite the fact it contains a few misspellings. Tell me, was there a single paragraph you didnB4t understood? Personally, I didnB4t found such. This is not an online english course and your comment is absolutelly irrelevant here. If your native language is english, maybe youB4d want to write some article in finnish or spanish maybe? I would...
ReplyOriginally posted by: Vlad
I found this article very useful and descriptive.
I've met one problem I could not resolve:
When I'm trying to create a new field "YesNo"(adBoolean type) in MS Access database I can not set Required property "Yes". I tried to use Attributes property like:
pColumnTarget->Attributes = adColFixed;
I tried to use also Properties collection:
pColumnTarget->Properties->GetItem("Nullable")->Value = false;
No matter what you set new field always created with the "Request" = No.
you cannot set nullable on a boolean field because it ALREADY is a not nullable field. by default it take the FALSE value. there is NO NULL in boolean field (it's a field exception) that's why you get error. however, what you're trying to do can be done setting the DEFAULT value propertie to TRUE.
ReplyOriginally posted by: ganti
I will be very much thankful to you if you tell how to get exact native sql datatype using ado and/or adox.
Though it covers all datatypes there are many repitetions, and not exact, same type no for smallint and int.
Thanks,
--Ganti
I'm not sure what you meant. although here the variable type that can be used in ACCESS 2000 using ADO adUnsignedTinyInt this is a signed short (byte) 0-255 adSmallInt this is integer up to 32767 adInteger 'This is a LONG type adSingle 'This is a Single type (Reel Simple in Access) adBoolean boolean adDate date/time type adVarWChar, string type, carefull you must provide a lenght with that one adLongVarWChar 'Memo Field hope that help...Reply
Originally posted by: Paul
I've used ADOX a couple times, but have found it lacks several features which would allow it to provide full DDL level support. While everything you presented is correct, sadly I've noticed that sometimes features which work alone do not work together.
I tried, for example, to add a table with a autonumber, indexed, primary key field....I couldn't get it to work! Any of the single parts worked, but not all together.
My suggestion is to stick with DDL. It works.
Reply