Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsReportsReportsReports Module and Microsoft Access 2003Reports Module and Microsoft Access 2003
Previous
 
Next
New Post
10/3/2012 4:07 PM
 

Let me start with the basic info... I am running DNN 6.2.1 with Reports 5.5.0.

I am using the Reports module to do some reporting out of a Microsoft Access 2003 database.  This has been working great and I am very pleased with the result.

I am having a problem with a new report and I'm not sure if it is the data provider, Access itself, the visualizer or what.

I have a query that runs fine in Access.  It contains two "calculated columns" that call functions I have in an Access Module to calculate the values.  These two columns come up blank (no data) when the Report is displayed.  All of the standard columns display fine.

Here are the specifics on the Reports module setup...

Visualizer: "XSL Transformation Visualizer"
Data source: "Generic ADO.Net Data SOurce"
ADO.Net Data Provider: "OleDb Data Provider
Connection String is "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=D:\Shared\Database\Hours.mdb"
Query" "SELECT * FROM BudgetCases ORDER BY [Office],[Employee ID1] ASC, [Case Number] ASC"

"BudgetCases" is the query I created in Access that contains the 2 "calculated columns" along with a number or regular columns.  I decided to use a query because of the calculated columns as well as the fact that it joins a number of different tables.  As stated previously it runs fine in Access (displays the two "calculated columns".

I suspect it the Jet Data Provider but I'm not certain.  Any suggestions would be greatly appreciated.

Thanks,
Chuck

 
New Post
10/3/2012 4:54 PM
 

UPDATE:

I did some additional digging and I think I verified that this problem is related to OLEdb or the Jet data provider. 

I started thinking that perhaps it was because the columns coming back are not named like I thought (when using a function you need to define the column using an alias). 

I decided to try loading the results of my query into Excel using "get external data" to see what column names comes through. When I selected my query in the Excel Query Wizard my calculated columns did not show up!

Next I assigned an alias to one of the standard columns in the query. After doing this, that column disappeared from my Report module report.  However, the column stills shows up in the Excel import but it shows the actual column name not the column alias.

So it appears that "calculated fields" (or at least those using vb functions) don't come through the OLEdb connection.

Still looking for a solution...

 
New Post
10/3/2012 5:30 PM
 
this might be a known limitation of OLEDB provider for queries from mdb files, I fear.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsReportsReportsReports Module and Microsoft Access 2003Reports Module and Microsoft Access 2003


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out