I'm running reports in MS Access 2003 which query against our SQL Server 2008 database. Unfortunately when adding new vies to the report form MS Access has begun crashing as soon as I try to view them in anything other than design view.
The program is not throwing out any error messages and the individual views cannot be displayed outside of the report form.
I have converted all of the views to tables as a rather sloppy hack to get these reports up and running. Although this works I'd really like to try and gain a bit more insight into why Access is willing to display some SQL Server views and not others. Note this is not an issue with 2003 I believe because the same behavior is observed in MS Access 2010.
Has anyone run into anything similar?
Any Ideas what may be causing this?
I'd like to avoid having to use my convoluted table conversion method in the future.
Related
I'm toying with the idea of migrating an office from Access 97 to LibreOffice 5. The problem is that the people in the office use the Designer in Access for Queries. They have made it clear that they won't learn SQL and as such as the IT I have to find a solution.
The issue arises when I do direct SQL in a LibreOffice Base Query. After using raw SQL I can't get the designer to kick back in for the office workers. Access can go between the two without an issue as long as I use proper Access syntax.
Is this a limitation of LibreOffice or am I over looking an option?
I had to untick 'Run SQL Command Directly' and then select 'Switch Design View On/Off' under view.
Good morning, All.
First let me start off by saying that I'm extremely new at CRM and even after reading umpteen million articles, whitepapers, and blog entries, I still feel completely lost.
I have an instance of Dynamics CRM 2013 On Premise that I'm trying to write custom reports for. Before I realized that all reports had to be done inside of BIDS, I wrote out a beautiful custom Quote inside of SSRS itself. I made sure to use the Filtered Views in my query to the database, and the structure of the query seems sound, but I can't seem to upload the .rdl file into CRM.
I get the error:
Reporting Error
Error occurred while setting the data source for the report
I have two questions:
How do I move this report into CRM without having to fully recreate it in BIDS?
How do I pass the Quote ID from CRM to this report query?
Thanks in advance for all of your help.
Edit: Added Error Message
You Should be able to upload the RDL directly to CRM...
Try creating a really basic report with the same data source and something along the lines of "select top 10 from filteredincident" and upload it.
If it works then you know it's something with your query.
CRM is notorious for giving error messages that don't have enough information, or are at worst misleading. I've seen this error when I accidentally used non filtered tables and a autofilter parameter that was incorrect.
Also take a look at the SSRS server that CRM talks to, if it's misconfigured that may cause an issue as well. You may want to try uploading your report to SSRS and run it from there to ensure that SSRS is working correctly.
I'm trying to rebuild an Access adp application in Access 2007. I started with a blank database, linked the SQL Server tables I need with ODBC, and then copied over all of the forms from the original application. I then updated the data sources for the forms to go to the correct tables.
When I open one of the forms, I get the error "Syntax error in WITH OWNERACCESS OPTION declaration". This error is occurring before the Open event code is being run.
Does anyone have any ideas about how to track down where this error is coming from? Or maybe an idea of another way to do this altogether?
Thanks!
WITH OWNERACCESS OPTION makes no sense in an ADP, as it's a command for Jet SQL for use with Jet user-level security. With an ADP, the security should all be set on the server. So, you should remove all the WITH OWNERACCESS OPTION statements from your form RecordSources.
Frankly, I'm not sure they have an effect in anything other than a saved QueryDef, so likely they were an error in the original application.
Also, I would never recommend copying anything from an MDB into an ADP. First off, I don't believe migrating to an ADP is ever advisable (though I certainly use ADPs as an administrative tool with my MDB/ODBC apps that use SQL Server), but secondly, there are so many differences between the two platforms that I just can't see them working.
If I chose to migrate an MDB to ADP (and I can't imagine that I ever would, given that MS has been deprecating ADPs for about half a decade now), I would start from scratch and rebuild it from the ground up.
My organization is in the process of upgrading from Access 2003 to Access 2007. One of the apps I am tasked with upgrading is returning very odd errors while opening and closing forms that have nested forms. Have the events changed between Access 2003 and Access 2007 ? The events seem to be firing in a different order in 2007 then they did in 2003.
I haven't encountered the situation you described. I can't find anything which mentions changes to forms event model. Allen Browne has some information about Access 2007 compatibility with older versions:
http://allenbrowne.com/Access2007.html#Compatibility
The only problems I experienced so far with 2003 MDBs in Access 2007 were due to broken references. If you haven't already done so, double-check yours (Tools-> References) from the VB editor. While there, try Debug -> Compile to verify whether your code will compile without errors in Access 2007.
Tony Toews' Corrupt Microsoft Access MDBs FAQ could help fix or rule out odd behavior due to corruption:
http://www.granite.ab.ca/access/corruptmdbs.htm
If you've done those things, and still have problems with certain forms, it might be useful to create a new blank database and import those forms (and objects they depend on) into the new database.
Sorry to scatter-shot this thing. It might help if you could provide more detail about the nature of the errors you're getting.
I've written an Access 2003 application to handle internal things at my company over the past couple years and we are talking about upgrading all of our computers to Office 2007 which means Access will be updated. Is this going to cause a problem for me?
Allen Browne, Microsoft access MVP, has written a comprehensive article on Microsoft Access 2007 and upgrading:
Converting to Access 2007
Here is an article by Microsoft:
Transitioning Your Existing Access Applications to Access 2007
In case you are not aware, it is possible to try 2007 for free. I would not recommend trying on a PC that you use regularly for other Access work, it is not impossible, but things get awkward.
If you wish to run your 2003 version on 2007, make sure that you create an mde, otherwise you will run into problems. Access 2007 treats several controls in a different way, for example, textboxes with date fields get calendars attached. You will also need to check your references. I also recommend that you self-certify your projects. Other than that, I have seen posts on a number of problems, but these are usually specific to the poster.
We just recently went through this.
One issue we found was converting reports to Excel. They took that functionality out of Access, so if you do that you'll need to convert it programmatically using the Excel COM object model. I ended up writing a function to replace the old functionality but you still have a bit of juggling to do.