I have created a custom Crystal Report (CR 11).  I built an RE query that feeds an RE export.  This RE export(Access 2000 database) feeds my Crystal Report.  In my Crystal Report I had to attach to the (Access 2000 database) twice to get the data paired up (So, have one table (regular name and an alias tablename).  All of this works fine separately.  I added the Crystal Report into RE on the Custom Report Screen.  I have setup up the export and crystal report files.

When I run it it all works fine (the Export runs and generates all of the records) until RE seems to want to know about the Alias tablename I created in Crystal Reports and stops the whole process with this error.

    Table '<alias tablename>' is required by report but not present in the export file.

If I run all the components separately, it all works fine.  The problem happens when I add the Crystal Report into Custom Reports.

Any thoughts on a way to get RE to accept this alias tablename....?

Mike, it may be helpful to take a look at BB98520. One possible cause is "The file was exported in Microsoft Access Database File format instead of Blackbaud Report Writer Database File format" so you may want to try changing the export format.

Hey i've struggled with this too, and I can make it work under certain circumstances.  If the alias table is in a subreport, it will work fine.  If it is in the main report, you will get this error.

So anytime i want to use a table twice like this, I make everything that involves it (or even the whole report) a subreport, and then in the table manager for the subreport, i add the alias table. 

Or if you have a report running great, but it is giving you this error in custom reports, make the entire thing a subreport and add it to a new report.

Of course if you already have subreports in your report you might need to rearrange things.  But like i said, under certain circumstances I can make it work.

So if you ever want to use a table more than one time, as an alias tablename, make sure you do it in a subreport.