I have an MS-Access 2013 application (.accdb) with only couple of tables and forms in it. I am trying to deploy it on another machine that has only MS-Access 2013 runtime installed. Problem is my access application opens up on that machine with a security warning but doesn't show any object in it. Not even access ribbon. What am I missing or doing wrong?
Solution suggested by #HansUp and then explained by #PowerUser in comments, worked like a charm.
Related
I run MS Access 2010 on my home PC and I've been building a database for work.
Most workstations at work don't run Access to build databases, but they do allow us to run MDE files for applications already built.
I saved my database as a 2002-2003 database and then published it as an MDE file. All worked really well. I tested the MDE file on my PC at home and the automatic re-linking to the back end db worked and the database popped up. Awesome.
The problem came when I tried to run it on the workstation. It came up with an unrecognized format and suggest I change the version on the database.
So, back to the drawing board. I did some research and from all indications from other forums and sites, you cant build MDE files for 2002-2003 databases using Access 2007 or 2010, even though the option is clearly there.
Suggestions were to load Access 2003 to the PC an build the database using this. OK, did that, imported all of the items from the 2003 database created in Access 2010 to a blank db created in 2003 and I get nothing but errors. Incidentally the database was originally build from and access 2003 database at work! Unfortunately, I no longer have access to that particular workstation.
So that's the dilemma. The question / discussion im after is how to resolve this and get the database, preferably from my office 2010 suite into a standalone system of some type working from a Windows XP workstation at work.
I need to find a way to be able to build these tools at home and use them at work. BTW, upgrading the workstations at work is not an option. believe me the organisation is too large to even consider a change like that, WAY too much bureaucracy..
As mentioned in one of the comments to your question, if you are targeting an older version of Access then you should be doing your development in that version, not a newer one. Even though Access 2010 allows us to create an .mde file that is in the Access 2003 file format, it may actually create an .mde file that Access 2003 cannot understand due to the contents of the file.
The situation is analogous to the problem of making certain modifications to an Access 2007 database in Access 2010+ that render it unusable by Access 2007. Even though the file format is still "Access 2007 or later", Access 2010 may create database objects within that file that Access 2007 cannot comprehend. Depending on the actual objects involved, Access 2007 may simply ignore what it doesn't understand, but unfortunately in some cases Access 2007 will just give up and say "Unrecognized database format".
After deploying my reports to the reporting server, I tried to add a subscription on one of my reports. It was not possible, and I got the error as described in this link.
http://www.kodyaz.com/reporting-services/subscriptions-cannot-be-created.aspx
All my reports use the same shared data source.
I applied the solution proposed in this link and it worked.
BUT Each time I deploy my reports (from SQL Server Data tools for Visual Studio 2013); the error comes back.
I tried to modify the properties of the shared datasource with SQL Server Data tools for Visual Studio 2013 before deploying;similarly to what is shown in the hyperlink, but in this case I am not able to access my reports anymore.
So, it seems that I could only modify the credentials "online" with my web browser; and not "offline" with SQL Server Data tools for Visual Studio 2013.
I remarked one difference between the "offline" and "online" properties of the shared data source : online, it is possible to check the box "Use as Windows credentials when connecting to the data source". This checkbox does not exist in SQL Server Data tools for Visual Studio 2013.
This means : each time I redeploy the reports from SQL Server Data tools for Visual Studio 2013, I have to do the online manipulation on my web browser to get the subscriptions working; which is of course really annoying...
Does someone know how to fix it?
Thanks in advance and sorry for my poor English.
I had a similar problem. I solved it by simply deploying the whole project and not only the shared data source.
I have a Access 2003 database that I want to store in source control on TFS2010. I'll be using the Team Foundation Server MSSCCI Provider 2010. Are there any rules for which versions of Access can create a database from that source? It's possible that Access 2010 and 2007 will be used to edit the source control. I'm curious as to if I should limit the versions of Access touching the source code to just a single version of Access.
The site of MSSCCI states to support Access 2007: http://visualstudiogallery.msdn.microsoft.com/bce06506-be38-47a1-9f29-d3937d3d88d6
On the same site, two other references from users can be found. One is stating that this version also works for Access 2003. Somebody else is experiencing that this version of the MSSCCI does not work for Access 2010.
A save bet would be to start your efforts with Access 2003, or if possible better with 2007. At least do an experiment with saving some 2003 stuff and opening it again with 2007 and vise versa. In time, I guess that support for Access 2010 will show up and you can continue from there on with newer version.
Hi I have a application designed in access 2003 that has its front-end and back-end split. The front-end has some tables used in the UI and a lot of queries, forms, reports, and macros. This app also has a custom menu bar based on the current state of the application. I am trying to open this app using access 2010 runtime (not the full access 2010) but the application is crashing right off the bat. I get a "Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down." Are there any common problems when running 2003 apps in a 2010 runtime that I could have possibily missed? Also what is the best way to troubleshoot this without using Access 2010 full version (I dont have it).
Thanks :)
Got it working. I just turned on compact and repair on close. Seemed to have fixed the problem (never was able to figure out wat it was though). The bug was only reproducible on Win7 and not WinXP
Anyone knows if it is possible to install Access 2003 standalone without the rest of the Office 2003? I seem not to locate my installation disks to test this out, but thought someone might have an answer...
I believe so, when you install Office and choose custom install, you can deselect everything except Access.
You can do a custom install and then deselect everything.
You will basically get all the MS Office run-time and shared components with only the Access application available to run.
Note: I don't use the access run-time any more, but do use it regularly for the Excel and/or Word applications.