Figured I'd throw this out here because in-house because in-house ITS and myself can't figure it out at all.
I have some Access 2007 front-end forms connected to lists in Sharepoint 2010. I updated the columns in a few of the lists in Sharepoint. On some workstations, the lists that were updated cannot be opened in Access anymore. However, they can still be opened directly from the Sharepoint web portal.
Does anyone have any idea what might be going on? Does Access have some sort of hidden cache of the structure of Sharepoint lists? We've tried all the obvious such as deleting and relinking and refreshing the culprit lists. All the computers in question are running the same version of Access and the same version of Windows.
Figured I would post what happened just for the record.
We are using Sharepoint Server 2010 and Access 2007. The problem was being caused by miscommunication between the two versions. We temporarily fixed it by installing Sharepoint Designer on all the workstations that needed the Sharepoint app, as this updated some of the Office 2007 files to Office 2010 and allowed compatibility with Sharepoint 2010.
Unfortunately, each time Microsoft rolled out an update to Office 2007, it broke the compatibility again, and after one update I was not able to fix it again. I have since moved to a MySQL/PHP platform and never plan on looking at Sharepoint again as a database platform.
Related
Is following scenario possible?
We have got TFS 2013 installed as a standard single server. This server has got the SQL db.
We have got SharePoint 2013 installed on another machine.
Now we want to integrate TFS 2013 with SharePoint 2013 along with SSRS and SSAS for reports, etc.
Please guide whether this is possible or we need to install TFS via Advanced mode again?
No problem, you can integrate your existing TFS single server deployment with your external SharePoint server assuming you have the necessary permissions.
MSDN: Verify your SharePoint installation
https://msdn.microsoft.com/library/dd578601(v=vs.120).aspx
MSDN: Set up remote SharePoint
https://msdn.microsoft.com/library/hh548140(v=vs.120).aspx
Cheers
Adding SSRS and SSAS is relatively simple too and can be on the same server as TFS or a different one.
MSDN: Add a report server
https://msdn.microsoft.com/en-gb/library/dn148128.aspx
Martin Hinshelwood has a couple of useful blog posts on this subject too:
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
*sorry for the multiple answers, new account and SO doesn't trust me to post 5 links yet! :)
I am getting the error This form template is not enabled for viewing in the browser. when I publish my InfoPath 2013 to my Sharepoint 2010.
Steps I have already followed:
Site Collection Features has "Enterprise Features enabled"
Site Features also has "Enterprise Features" enabled
Forms Library has "View as Web Page" enabled in advance settings
Infopath Forms Service has Render and User Browser Compatible Forms enabled
Set Compatibility mode in InfoPath to Web Browser Form 2010
I have made a blank form just to test if it will publish, but I am receiving the same error.
Concerns:
Does it have to do with anything with publishing from InfoPath 2013 to Sharepoint 2010?
Please let me know if there is any confusion in the question.
Did this process used to work and now it has stopped working? Have you successfully published and used a form with this method?
A user here reported this same error yesterday, and it is one I've never seen before. Apparently, our company's updates of Microsoft patches installed a portion of Office 2010 on this person's system. Once this was uninstalled, InfoPath returned to working as normal.
(We also publish InfoPath 2010-compatible forms from systems running Office 2013.)
This may not be related at all to your problem, but since we saw this symptom just yesterday, I figured it might help.
Paul
As there is a drastic change in architecture from SharePoint 2010 to 2013, I would like to know what are the restrictions for a developer while developing Solutions/Apps for Office 365.
In SharePoint 2010, only sandbox solutions were allowed on Office 365, but in SharePoint 2013 the sandbox solutions are depreciated and App model is introduced. Would be glad if someone can throw some light on what is allowed and what is restricted on Office 365 in the new 2013 environment.
Sharepoint 2013 is a game changer, starting with the fact now is possible to use framework 4.5 and, since the new release of visual studio 2013, it's possible to use MVC. From a developing point of view you have to know there are two flavors:
Sharepoint hosted. In this case, your whole application is installed within the Microsoft servers. Because of this, you MUST use client object model and javascript. No server code at all. So you will configure your sites, libraries, lists, etc with 365 and then access this information using the Sharepoint javascripts libraries. If you are familiar with js ans sp js the you won't have any problem.
Autohosted. In this case you can choose between azure or your hosting (provider hosted) in both cases you can use a more traditional aproach, with your server code, classes, aspx and so on. The difference is when you deploy your application, in this case the app is installed just as a reference in 365 and all the code in your hosting provider. In fact all your application will be displayed in 365 within an iframe. Keep in mind you will be dealing with lots of cross domain scripting.
Last but not least, you have one final flavor, but it's not 365, Sharepoin onpremise, in this case this is your own sharepoint, you create, manager, develop or deploy whatever you want. This is very similar to the current sp2010 model, so, I guess you already now what you can do.
For more information:
http://msdn.microsoft.com/en-us/library/office/apps/fp179930.aspx
http://blogs.msdn.com/b/amigan/archive/2012/12/10/part-2-introduction-to-sharepoint-2013-app-model.aspx
I am using Sharepoint Designer 2007. I cannot add new workflow or amend existing workflow. I am using Windows Server 2008 R2. I have tried the following post. But I cannot get the directory specified.
Other users can access the workflow, but it happens only for me.
Tried This Link
Did anyone have this issue.
Try to update your office 2007 with the latest Microsoft patches. I remember having this problem before but don't remember how I fixed it! :(
I am supporting a legacy application that was written in Access 2003 using VBA. We are updating our systems to Office 2010, with the exception of Access, which will remain the 2003 version. (This is due to several factors pertaining to other groups in my organization.)
We use Access as a front end for running reports out of MS SQL and Sybase databases. Some of these reports open in Excel. During testing, running reports that write to an Excel workbook causes the Access application to crash and exit without a warning message - the application simply disappears from the screen.
I'm not sure what the cause of this is or where I should start looking for answers. Has anybody dealt with a similar situation?
I saved and recompiled the application on the development machine that had Office 2010 installed, and thereafter the application worked correctly with Office 2010 (of course, it no longer works on machines only having Office 2003.) This was, of course, after checking the references were correct. Without any intervention, the reference to Office was for 2010.
After testing with early versus late binding, it would appear the best answer to this issue is to use late binding.
Make sure you are writing to Excel in Excel compatibility mode (.xls).