Help in change the ordinal position to ado

Question

4.00/5 (1 vote)

See more:

I have to change the ordinal position in ado we have put_OrdinalPosition API directly in DAO mfc but as dao will not support 64 bit we are changing to ADO but they are no apis to changed ordinal position.

Could you please let me know any idead about how to implement in ADO C++?

What I have tried:

DAOField *pField = Get_DAOField(lpszTable, lpszField);

if ( pField )
DAO_CHECK(pField->put_OrdinalPosition(ordinal));

how to changed to ADO?

Posted 27-Apr-21 20:27pm

Member 13798855

Updated 28-Apr-21 1:16am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2021-04-28T01:16:00

The tiny small difference in character order is misleading to the big gap between the technologies.
The best solution is to get rid of this call by removing the need of that change of the data structure. Maybe it is only a fix for some old bug or some weired data fetch. Else you may change the data fetches which are using.
Last fix is to create a view or table with that fix in run time or swap after creation.

All not good solution, BUT the cause it that nasty and incompatible call. I prefer removing it by removing the causes from them.

Good luck.