Crystal Report Error to Connect to Native Database

wayosakorn

I use Standard Report Wizard in Crystal Report 11 , when i connect to the native database with ODBC, some Table I can select it but some Table I cannot select it (such as Sales Header).

The error is "Database Connector Error : '22003:[Microsoft Business Solution Aps][Microsoft Business Solution-Navision ODBC Driver]Out of Range [Database Vendor Code: 1011]' "

So I had to test it, And I found that Table Sales Header has more Column or Field. If the table has only 30 columns or fields, The Crystal Report can select the table.

Do you have any idea for solving my problem?


Thanks
P o N

Savatage

wayosakorn wrote:

So I had to test it, And I found that Table Sales Header has more Column or Field. If the table has only 30 columns or fields, The Crystal Report can select the table.

My Vendor table has 118 fields - access no problem

1)create a blank report
2)create a new connection
3)ODBC (RDO)
4)Select data source (you should see the source you created with c/odbc)
5)Login & you tables should appear.

I have also setup my c/odbc setup options as
commit cache ->YES
DBMS Cache (KB) 100000
Enable Blob Fields->YES
Identifiers->All Except DOT
Option Field Type->TEXT
Language->Auto
Query Time Out->NO
Query Time Out->"Blank"
Read Only->NO
Tmp Path->"Blank"
Closing Date Support->No
Use Regional Decimal Symbol->No

mabu

You have to use OLE DB (ADO) instead of ODBC then it will work fine

rj5570

how do you set up OLE DB instead of ODBC? i keep getting an error when i do that.

and i am still getting the connector error vedor 1011 when i set up ODBC like above

please advise

Savatage

I think he ment you have a choice in Database Expert of many ways to get data.

I use the ODBC (RDO) but that works for me.
Try the OLE DB (ADO) is you have problems as suggested above.

see pic
http://savatage99.googlepages.com/Cryst ... ctions.JPG
(enlarge for clarity)

Your C/odbc or n/odbc should be setup normally - the connection change is in Crystal not in the odbc setups

rj5570

thank you for the response.....

thats were i was trying to do it, and i was gettin my error

this is what i am doing, onec i get to that screen you should me

i select Microsoft OLE DB provider for ODBC drivers

i select the ODBC connection I have set up to Navision

this is the error i get, its long

logon faild
details ADO error code: 0x
source Microsoft OLE DB Provider for ODBC Drivers
Description : [Navision a/s][Navision attain ODBC Driver]data source rejected establishment of connection SQL State: 08004
Native Error: [database vendor code: 1058]

Savatage

So you tried both ways? and your sure your n/odbc has been installed correctly and is the same version as your database?

rj5570

yes, i installed the ODBC driver from my navision install disc (i am currently running 3.6, havent upgraded due to i need to be sure the upgrade works with RMI Rental Advantage, and havent had the time to research)

rj5570

i am not using SQL by the way, i am using the Navision server

Savatage

step one is to make sure your license has Granule 1,700.
Tools->License Information

Else you can't use it.

I never had problems with the regualr c/odbc setup so I never tried the Ole DB path.

But as I look at it - you double click on OLE DB(ADO) it should give you a list of providers. Try choosing "Microsoft OLD DB Provider for ODBC Drivers" then when you hit NEXT it should bring you to your c/odbc driver you setup! Select & hit next - ender your User ID - hit finish.

I can connect that way too.

rj5570

yes i do have the granule

i can connect with the ODBC connection in the database wizard but i get this when i try to connect to the G/L Account table

"Database Connector Error : '22003:[Microsoft Business Solution Aps][Microsoft Business Solution-Navision ODBC Driver]Out of Range [Database Vendor Code: 1011]' "


Thats why i tried the other. I can connect to other tables, but i get the above error on some tables.

frustrating eh?

Savatage

in contraol panel->Adminstrative tools->data sources

install the c/odbc in UserDSN & System DSN identically - see if that helps :-k

rj5570

NOPE

that didnt work either ](*,)

Savatage

when you click on the C/odbc driver you created & click configure then company - does it let you login? if so when you click on the options button do you have it configured as I have mine listed in the the 2nd post?

It sounds like you're in the ballpark but one thing isn't setup correctly ](*,)

rj5570

yes i do.

like i said, i can run a report on some tables, but some of them i get the error from the first post in this thread.

and i can not do the OLE DB (ADO) like mabu did.

really ODD!!! ](*,)

Savatage

But as I look at it - you double click on OLE DB(ADO) it should give you a list of providers. Try choosing "Microsoft OLD DB Provider for ODBC Drivers" then when you hit NEXT it should bring you to your c/odbc driver you setup! Select & hit next - ender your User ID - hit finish.

Well the last thing I can think of is follow the C/odbc setup doc that comes with on the product cd and see if you missed something.

Is it just the huge tables that you have trouble with?
what version of crystal are you using - & did you get all the updates & hotfixes?

rj5570

i was using version 8 for awhile...but i was having trouble with date/time ranges so i downloaded the trial version of XI before buying it.

if i get this working i am buying it ASAP

i will try that!

i might give up for the day and try and post again tomorrow, thank you

rj

rj5570

curious, what would keep me from opening large tables?

should i be looking server side?

i am really ](*,)

rj5570

OK!!!! I GOT CONNECTED TO THE TABLE FINALLY!

this is what i had to do

when i set up the ODBC, i did not set up as a User DSN, but as a System DSN only.

under options, I left EVERYTHING as default EXCEPT identifiers set as: a-s,A-Z,0-9_

after that, i connected thru the data wizard as OLE DB (ADO)

BINGO! i was able to connect to the large table as i was trying to do before.

Hopefully this helps others too!

rj

Savatage

I knew you were close - sometimes a little trial & error is all you need to figure out a problem.

\:D/