Oracle EnterpriseOne (E1) & MS Access
Unfortunately, we have users that like to use other applications to access our Oracle JD Edwards EnterpriseOne (E1) data. I say, "unfortunately", because when users view data outside the application, you never really know if what they are looking at is really what they want to see. Of course, this is dependant on the expertise of the user.
Anyway, we found a limitation on one of our users favorite little helper applications, Microsoft Access. There is a limit to the number of indexes a file can have that MS Access links to. That limit is 32. Which, in most cases is plenty. Our F06116 has 32 indexes, but was still not able to be linked to. I think it is because MS Access counts the actual file as one of the indexes.
Hope this helps someone else dealing with Oracle JDEdwards EnterpriseOne (E1) file access with Microsoft Access.
Here are some other Microsoft Access limitations.
Author
Stewart Schatz
More Stories
Quick Tip: IBM Navigator for i Default URL
This is a really quick one but I keep forgetting it: http://<SERVERNAME>:2004/ibm/console
Server Manager Agent Not Connecting To SMC
After a Java update, the server manager agent may not connect to the SMC because of parameters in the java.security...
Quick Tip: How To Delete Multiple SQLPKGs
Run the following command to delete all the SQLPKG's in the QRECOVERY library with a name beginning with "OW" DLTSQLPKG...
Quick Tip: IBM i (iSeries / AS400) Spool File Navigation
The following commands can be used to navigate spool files after using a command similar to WRKSPLF. Just enter the...
Needle: IBM iSeries (AS400) Power Outage JDE Recovery
Crazy to think but this issue has come up a few times in my years as an Oracle JD Edwards...
Quick Tip: Limit The Number Of Rows Returned From A SQL Query
This is pretty basic, but I had to look up the syntax to use for SQL on IBM DB2 so...
Average Rating