Hi all,
1) Can open database connector be used to connect to navision? If Yes/No, does it have limitations?
2) Do i need purchase NAV connector apart from Open Database connector to connect to NAV, what advantages i will have using NAV connector
Date
Votes
2 comments
-
Jet Reports Historic Posts Hi there.
I don't have the open database connector (I presume you mean ODBC), but I'll answer your questions based on what I know of the existing Nav connection. Keep that in mind when you read my responses (disclaimer).
I'm sure others like Jan and Hans will possibly have a better explaination/answer.
1) Yes, as long as your Navision DB is in SQL Server. It may be possible to use with NAV if your DB is native, however I would think it might not perform that well if it did work.
2) The biggest advantage of the NAV connector is access to a bit of the 'logic' that NAV uses. For Example, if you use the NAV connection, the Item card has a field called Sales$. This appears as an element on the Item table, however its actually a flowfield (I think thats the correct term). So when you use the open database connector you do not have access to that field, so you would have to do the calculation manually.
A disadvantage of the NAV connector (as I see it) is it uses the NAV API to issue its requests, so it uses a Nav license when a report runs. If you're close to your license limit, this could be an issue for you.
For us, we used the NAV connector because it was cheaper, and we were on the CSIDE database at the time we purchased Jet.
You'll probably find some other posts around that would shed some more light on the pros and cons of each connector type. Similarly I'm sure Jet have sales persons that would be more than happy to answer your questions (probably the best place to start).
cheers, Mark -
Jet Reports Historic Posts Hey,
What mark said is absolutely correct.
However, I'd like to add some extras on the pro's of the NAV connector (vs SQL connection):
- Support of Companies (working with companies, switching companies is quite hard when using the universal connector)
- As mark said, flowfields & flowfilters
- G/L Functions (with dimensions)
Some issues are, as everything goes throug NAV:
- C/FRONT has to be installed
- Performance might not be as goodµ
- Again, as mark said, it'll cost you a license for a Jet User, however this is always only during runtime/devtime
I'm sure there are people with more experience with the universal connector who can answer your questions better.
Tell us, are you using a native NAV or an SQL one?
Please sign in to leave a comment.