I had an image, but I don't have enough reputation to post it. The error is as follows:
Database Connector Error: 'DAO Error Code: 0xbe4
Source: DAO.Fields
Description: 'P:\db\Name.mdb' is not a valid path. Make sure that the
path name is spelled correctly and that you are connected to the server
on which the file resides
I have been tasked with converting a good many Crystal Reports to SSRS. Unfortunately, I can not get the path of my first report to change to where it is now located on my computer. I have been trying to get into the code, but this error pops up when I try to look at the SQL, when I try to preview the main report, and when I try to verify the database.
We have copied this .rpt and the access database file directly from the company we are doing this for, but it will not work. I can't even find this path ANYWHERE I've looked or with the find function, and when I look at the properties the correct path is there. I don't understand what is wrong.
I do know that CR has a lot of issues, especially moving around on machines, but I've never dealt with anything like this before.
Any help to resolve this error so I can begin working on these reports would be greatly appreciated.
Just Google "Crystal Reports to SSRS" and you will find solution to convert Crystal to SSRS automatically.
If you like to have a try, you may send your report to support#crystalmigration.com
Most Crystal Reports can be perfectly automatically converted to SSRS.
Related
Im making a simple application in C# using Visual Studio and WinForms.. I’m using SQLite as my database.. When I use the Run feature within Visual Studio, everything works 100% beautifully.. The problem arises when I install my program onto another computer.
When I install and run my program in another computer, at first, everything works great. Things that require select statements work perfectly.. However, when I try to do something that adds a row to a table or modifies an existing row, my program crashes with the following error: “Attempting to write on a Read-Only Database.”
Upon doing some research online, I realized that this error wasn’t 100% accurate. The database is read-write.. However, the folder containing the database is read-only. So I guess I have to move my database from this read-only folder, to a read-write folder somehow.. How do I go about doing this? Which folder is it in currently, which folder should I move it to, and how do I prevent this move from causing any errors?
This answer identifies the problem, but doesn’t give a clear solution:
https://stackoverflow.com/a/16068894/10216226
Please help me out! I’m at the final stretch of developing this application and I really would love to have this completed!
Thanks!
I have recently taken a project for a client which involves working with their Microsoft Access database programmatically with C# in Visual Studio 2015/2017.
The database opens in my 64-bit version of Microsoft Access 2010 just fine, and I can use/alter all tables/queries perfectly fine. However, when trying to open this .accdb database in Visual Studio, I am getting the dreaded "Unrecognized database format". Now, I do have the Microsoft Office Access database engine for 2007 and 2010 installed, and I am able to open/work with other databases created in Access.
I believe the database was created in Access 2007, as when I open it up, the title of the window contains "(Access 2007 - 2010)", so I'm not sure if that would cause the error or not?
One interesting thing I found was, because I do not need every table in the database, I copied one by one the tables I need into a new database file and checked if I could open this new Access database in Visual Studio. Out of 6 tables that I needed, the last one I needed caused the file to become "unrecognizable" inside Visual Studio.
Why? I have no idea. The table is just like any other, contains lots of columns which either have text, numbers or dates.
My question is, has anybody had a similar experience with this? Could it be the fact that it was made from Access 2007? Why would copying and pasting to a new database then cause that database to be corrupt?
Thanks a lot.
There's a difference in the formats. The older format (..2007) is MDB and the later ones (2010...) are ACCDB. If you used any features only available in ACCDB, like attachments, you cannot convert back to MDB and neither will ANY current Microsoft tool other than Access open it. Strange but true.
Painful is to exclude those tables or forms that use the new features and then do the conversion.....sigh.....
We recently upgraded from Excel 2007 to Excel 2010, and we have found that existing code started failing.
Exception Message:
Office has detected a problem with this file. To help protect your
computer this file cannot be opened.
We have traced this to the line where we open the file
excelApp.Workbooks.Open
Even when opening the file manually, the Protected View Messagebox comes up.
How can we work arround this using C#.
Have a look at using Application.FileValidation Property (Excel) before your Open statement.
Returns or sets how Excel will validate files before opening them.
Read/write
Files that do not pass validation will be opened in a Protected View
window. If you set the FileValidation property, that setting will
remain in effect for the entire session the application is open.
You can set it to one of the enum values in MsoFileValidationMode Enumeration
msoFileValidationDefault
msoFileValidationSkip
if you set it to msoFileValidationSkip before the Open statement, it should bypass the check.
Something like
excelApp.FileValidation = MsoFileValidationMode.msoFileValidationSkip;
before the open statement.
Late to the game here, but this is a common annoyance: you need to define a 'Trusted Location'.
You're not the only developers encountering this problem when your code tries to open a spreadsheet file, and "Office has detected a problem with this file. To help protect your computer this file cannot be opened." is an extremely unhelpful error message.
Look up the Trusted Location code published by Daniel Pineault on DevHut.net in 2010:
DevHut code example: Trusted Location using VBScript
I'll get downvoted to hellandgone for posting VBA in a C# forum, so I'd better not post my implementation of Daniel's code (yes, I'm a VBA developer, bashing out VBA macros all day, not a real coder working with pointy things and curly braces). If you really want to see the VBA, it's in a reply to another post:
https://stackoverflow.com/questions/2962728/office-trusted-locations/28115700#28115700
I believe the proper salutation is 'Share and Enjoy'.
Do, please, put an acknowledgement of the original author, Daniel Pineault, if you reuse the code: it's been widely published without attribution on 'Expert' sites, and that's rather rude.
We had the same issue. Our SSIS package at SQL server uses Excel.Interop to parse files. One day we installed Office 2010 x64 on new server and for some files started getting error:
Office has detected a problem with this file. To help protect your computer this file cannot be opened.
At the same time, other servers work good. We found distinguish in versions of Excel: 14.04763.1000 doesn't work, but 14.0.7015.1000 works for us. The last version number belong to Office 2010 SP2. Eventually we downloaded SP2 and installed it,as result, the error has gone.
I'm trying to deploy an application to a client's server, but export to Excel (Data Only) is not working, giving me the "Operation Not Implemented" error. It isn't a problem with the report, because I have over 50 reports with standard fonts, some of them very simple, and the export fails for all of them.
I have the feeling the incorrect version of exportmodeller.dll and crtslv.dll are being used, because the client seems to have some sort of logon script which appears to copy a CR8.5 version of the crystal reports libraries and register them with COM.
I attempted to automatically make a manifest file for my main executable to force it to use the correct version, but this didn't change anything.
Might I have missed something, or do you think I'm completely on the wrong track?
I narrowed the problem down to being related to a format issue with the report. It just happens to not affect my Windows 7 dev machine.
On the Windows Server 2003 R2 (x64) machine, if I remove the Print Date and Print Time special fields, it will export to xls (Data Only) successfully.
I did also notice that the process loads ATL.DLL on the Windows 7 box, but not the Windows Server box. I gather that could somehow be related.
So, a solution to my problem is to remove those fields. Full points if anyone can offer some advice which would prevent me from having to edit all of my reports.
Update: If I use a specific date/time format in my reports instead of "System Default Format" it also works.
I'm trying to export the reportsource of a crystal report viewer in .Net 1.1 onto disk as a PDF using
CrystalDecisions.CrystalReports.Engine.ReportDocument cr = (CrystalDecisions.CrystalReports.Engine.ReportDocument)crvView.ReportSource;
cr.ExportToDisk(CrystalDecisions.[Shared].ExportFormatType.PortableDocFormat, #"C:\Temp\Temp.pdf");
I know it's the "cr.ExportToDisk..." line thats failing, but dont know why.
Ive checked to make sure the Crystal Report versions are the same on the client machines and they are.
Sometime i get the message "Memory could not be read at source...." and the application completely crashes, and other times the app crashes without the message.
Any ideas on why this happens and how to fix it would be greatly appreciated.
Cheers
You may check to make sure that the security permissions are the same for the locations that you are trying to export to.
Are you able to print these "faulty" reports? If so, have you tried printing to CutePdf which might allow you to at least work around the issue temporarily.