Microsoft Access 2013

How to collect data in Microsoft Access 2013 via email with Outlook?

Hi Elango,
Since the issue is related to Microsoft Access , I would like to recommend you post the question in the Access for Developers forum at
https://social.msdn.microsoft.com/Forums/office/en-US/home?forum=accessdev . It is appropriate and more experts will assist you.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Similar Messages

Microsoft Access 2013 Database Invoice

I am trying to use a Database Invoice template provided by Access 2013. I am having trouble making some vital alterations, including making values non-dependent on each other.
For example, I don't want the total price to be dependent on the hours tab. I would actually prefer if the hours tab wasn't even there.
I can submit a screenshot if need be.
Thank you very much for your assistance.

Hi,
Which Database Invoice template do you use? I find Access 2013 provide 6 template which include the invoice.
And then I download one of them (Desktop Product inventory database) to customize the invoice report.
Right click invoice report > Choose design Mode
If I misunderstand something, please let me know and upload some screenshots.
Regards,
George Zhao
TechNet Community Support

Access 2013 Web reporting seems to be missing

I have a simple request from a user to print out a list of the database in a nicely formatted form. Should take 10 minutes (or so I thought). The version is Access 2013 web.
It appears that this simple request is not easily done. There appears not to be a reporting function in the Web version of Access. I spent a long time looking for it and decided that it just isn't there.
For my second choice I decided to deploy the desktop version and create the reports there, but can't get a connection to the SQL Server where the Access Web App stores my data in SharePoint.
I found a web link showing me how to hook up Excel to the SQL server supporting the web app database. I have gone to the Web Access FILE\INFO screen and selected the Manage Connections section. Followed the instructions
for enabling a read only connection and then copied and pasted the server, database name, username and password into Excel using the "From other sources" button, then selecting the "From Data Connection Wizard", Selected other/advanced
and then SQL Server Native Client 11.0. It does not find the server when I test the connection. I constantly get a time out.
I am using a 365 SharePoint server to host my access web site. I called 365 Tech support and spent hours trying to work this out with people that didn't know anything about Access. The SharePoint people didn't understand the problem of not
being able to connect and was eventually told that it wasn't a feature they offered.
As an aside, with 18 years experience in developing Access applications, I am looking at other products to replace Access. I didn't jump into Access 2010 web because of the way SharePoint handled the database, but this is worse. Hate to walk away
from the experience I have, but seems I have been left little choice.

See if this blog post that our support team created helps you with the connection information. This can create the desktop Access application linked up to the Access 2013 web app tables you have.
http://blogs.technet.com/b/the_microsoft_access_support_team_blog/archive/2014/03/24/how-to-make-external-connections-to-an-access-web-app-new.aspx
Also, you might just try clicking the Create Reports button in the Access web app client interface and Access will create the reporting database for you with links to the web app tables. On the File menu (when using the Access web app in client) make sure
to click the option to Allow Any Location under the Manage button. After that, just click the Create Reports button on the File menu (right above the Manage button) and wait a few seconds. Access will create a new desktop database linked up to all of the Access
web app tables. You can then create as many reports or other desktop objects as you like.
Hope that helps,
Jeff Conrad - Access Junkie - MVP Alumnus
Senior Content Developer - Office Content Development Team - Microsoft Corporation
Author - Microsoft Access 2013 Inside Out
Author - Microsoft Access 2010 Inside Out
Co-author - Microsoft Office Access 2007 Inside Out
Access 2007/2010/2013 Info: http://www.AccessJunkie.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/en-us/legal/Copyright/Default.aspx

Cannot add new column in Access 2013

I am using Microsoft Access 2013, and I am unable to add a new column to a table in Design Mode. I can add a new column in Datasheet Mode, but not in Design.

Hi,
From your description, I tried to do in my computer.
First, I open table1 in Datasheet Mode.
Rename a neo column.
Second, I right-click table1>Design View>Enter Field Name(Date type)>View> Datasheet View
I find that it works fine.
So I suppose that your Access2013 was damaged.
I recommend that you can use Access2013 in safe mode.
If it works fine in safe mode, you can repair Access2013.
I hope it’s helps

Can't Edit Data in Access 2013 Web App

I have an Office 365 P1 account that I have been using to create apps in Access 2010. I tried Access 2013. But when I launch an app, it loads in my Office 365, but editing data is not enabled (the Add and Edit buttons are displayed, but not enabled).
I have tried creating a new custom web app with one simple table and a view, as well as creating one using a Microsoft pre-built template, and simply creating the app and launching it. In both cases, the app displays, but I cannot add or edit data.
Is there something with my Office 365 account that is limiting my ability to work with Access 2013 web apps?
Thank you!

Hi KrisMarshall7,
In regarding of the issue, please provide us more information to assist you better.
What the file format is your Access 2007 file? MDB or ACCDB?
Where do you want to add the columns? Table, form or query?
As far as I know,
the limitation of columns in a table is 250. Thus, I suppose that the database had some hidden columns. Please try to check it. Steps:
Right-click any field title, then select Unhide Fields. A dialog box will appear. Click the check boxes of any fields you would like to be visible again, then click Close.
Hope it's helpful.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Can't Find ODBC drivers to link MS Access 2013 and MySQL

Can't Find ODBC drivers to link MS Access 2013 and MySQL.
Is one available?
Thanks,
Larry

Could to associate the problem at Office 2013?
I just installed the ODBC Driver; The data source machine was available; When selected I had received the message. When it was selected I had received the message:
"ODBC -- falha na chamada.
[Microsoft][ODBC Driver Manager] O DSN especificado contém uma incompatibilidade de arquiteturas entre o Driver e o Aplicativo (#0)"
In english, could to say: "ODBC -- fail on call.
... The specified DSN contains a architectural incompatibility between Driver and App (#0)"
I don't know yet the reason for this. Anyone knows?

Access 2013 crashed when I export a table from the access

Hi!
Access 2013 always crashed when I export a table from the access to the Database Symfoware.
1、The conditions of the Access 2013 crashed are the follows.
1)Create a table in the Access 2013.
2)Using the ODBC driver of the Database Symfoware to export the table from the access to the Database Symfoware.
2、The Environments are the follows.
1)Access 2013 X64(Version:15.0.4420.1017)
2)Win2008R2 X64
3)Symfoware V11.1 X64
3、The Application log from the Win2008R2 are follows.
ログの名前: Application
ソース: Application Error
日付: 2014/04/18 16:21:06
イベント ID: 1000
タスクのカテゴリ: (100)
レベル: エラー
キーワード: クラシック
ユーザー: N/A
コンピューター: WIN-29UTU2AIK6J
説明:
障害が発生しているアプリケーション名: MSACCESS.EXE、バージョン: 15.0.4420.1017、タイムスタンプ: 0x50674523
障害が発生しているモジュール名: ACECORE.DLL、バージョン: 15.0.4420.1017、タイムスタンプ: 0x506742b7
例外コード: 0xc0000005
障害オフセット: 0x0000000000171f36
障害が発生しているプロセス ID: 0xb6c
障害が発生しているアプリケーションの開始時刻: 0x01cf5ad638668c5b
障害が発生しているアプリケーションパス: C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE
障害が発生しているモジュールパス: C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL
レポート ID: 00e87957-c6ca-11e3-ad2c-0050568d2ced
イベント XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-18T07:21:06.000000000Z" />
<EventRecordID>3442</EventRecordID>
<Channel>Application</Channel>
<Computer>WIN-29UTU2AIK6J</Computer>
<Security />
</System>
<EventData>
<Data>MSACCESS.EXE</Data>
<Data>15.0.4420.1017</Data>
<Data>50674523</Data>
<Data>ACECORE.DLL</Data>
<Data>15.0.4420.1017</Data>
<Data>506742b7</Data>
<Data>c0000005</Data>
<Data>0000000000171f36</Data>
<Data>b6c</Data>
<Data>01cf5ad638668c5b</Data>
<Data>C:\Program Files\Microsoft Office\Office15\MSACCESS.EXE</Data>
<Data>C:\Program Files\Common Files\Microsoft Shared\OFFICE15\ACECORE.DLL</Data>
<Data>00e87957-c6ca-11e3-ad2c-0050568d2ced</Data>
</EventData>
</Event>
4、When the access crashed,I got the dump file .Then I use the Windbg got some information from the dump files.
The detailes are follows.
FAULTING_IP:
+58872faf03d6dd84
00000000`00000000 ?? ???
EXCEPTION_RECORD: 00000000001723c0 -- (.exr 0x1723c0)
ExceptionAddress: 000007fee3951f36 (ACECORE+0x0000000000171f36)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
FAULTING_THREAD: 00000000000010b8
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: MSACCESS.EXE
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ACECORE
FAULTING_MODULE: 0000000076eb0000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 506742b7
ERROR_CODE: (NTSTATUS) 0x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
MOD_LIST: <ANALYSIS/>
CONTEXT: 0000000000171ed0 -- (.cxr 0x171ed0)
rax=0000000001be3598 rbx=0000000000000000 rcx=01cf5d1b0f402a5c
rdx=0000000009cfad30 rsi=0000000006688ef0 rdi=0000000001be35d0
rip=000007fee3951f36 rsp=0000000000172490 rbp=00000000001727a0
r8=0000000009b409d0 r9=0000000006688ef0 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000001be19f0
r14=0000000009cfad30 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
ACECORE+0x171f36:
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12 ds:00000000`00000000=????????????????
Resetting default scope
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 000007fee395c095 to 000007fee3951f36
STACK_TEXT:
00000000`00172490 000007fe`e395c095 : ffffffff`ffffffff 00000000`00000000 00000000`01bddaa2 ffffffff`ffffffff : ACECORE+0x171f36
00000000`001727b0 000007fe`e388f8eb : 000007fe`e399dc10 000007fe`e399dc30 000007fe`e399dc50 00000000`000000f9 : ACECORE+0x17c095
00000000`00172b50 000007fe`e388f590 : 00000000`06688ef0 00000000`00000004 00000000`000000f9 00000000`00000000 : ACECORE+0xaf8eb
00000000`00172ba0 000007fe`e388f406 : 00000000`00000004 00000000`000000f9 00000000`11cb1130 00000000`000000f9 : ACECORE+0xaf590
00000000`00172c30 000007fe`e391aee7 : 00000000`00000000 00000000`00173198 00000000`06688ef0 00000000`11cb0998 : ACECORE+0xaf406
00000000`00172c70 000007fe`e3933a72 : 00000000`00400100 00000000`00000002 00000000`00000001 00000000`06688ef0 : ACECORE+0x13aee7
00000000`00172e50 000007fe`e384e5b1 : 00000000`00000000 00000000`11cb0020 00000000`06688ef0 00000000`00000001 : ACECORE+0x153a72
00000000`00172e90 000007fe`e38358d1 : 00000000`000007ff 00000000`06688ef0 00000000`01bd99f0 00000000`00000000 : ACECORE+0x6e5b1
00000000`00173280 000007fe`e38718eb : 00000000`000007ff 00000000`06688ef0 00000000`11cb0000 00000000`00000000 : ACECORE+0x558d1
00000000`00173340 00000001`3f3b0cd2 : 00000000`0a0945c0 00000000`000000fe 00000000`000007ff 00000000`00000000 : ACECORE+0x918eb
00000000`00173430 00000001`3f3b0b9b : 00000000`00173730 00000000`001741e0 00000000`065e5b00 00000000`00000100 : MSACCESS!CreateIExprSrvObj+0x16af32
00000000`00173630 00000001`3f3afcea : 00000000`00173730 00000000`00000000 00000000`00000000 00000000`065e5b00 : MSACCESS!CreateIExprSrvObj+0x16adfb
00000000`001736a0 00000001`3f983140 : 00000000`00174401 00000000`0a3235e0 00000000`0a319aa0 00000000`00179fc8 : MSACCESS!CreateIExprSrvObj+0x169f4a
00000000`00174290 00000001`3f3aabeb : 00000000`00000000 00000000`00000000 00000000`00179f38 00000000`00000000 : MSACCESS!FUniqueIndexTableFieldEx+0x26ab4
00000000`00174530 00000001`3f3a9670 : 00000000`001778e0 00000000`00179f38 00000000`00000031 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x164e4b
00000000`00177870 00000001`3f3a8c1b : 00000000`00000010 00000000`108c5990 003d0044`00570050 00000000`74ac3f69 : MSACCESS!CreateIExprSrvObj+0x1638d0
00000000`001779d0 00000001`3f5450df : 00000000`0a0945c0 00000000`0000009c 00000000`0a0945c0 00000000`00000000 : MSACCESS!CreateIExprSrvObj+0x162e7b
00000000`00179e30 00000001`3f64e915 : 00000000`43ed8000 00000000`00000000 00000000`3f800000 00000000`00000000 : MSACCESS!FillADT+0x5830b
00000000`0017c450 00000001`3f33b172 : 00000000`00000000 00000000`0006075e 00000000`0017e370 00000000`00000000 : MSACCESS!IdsComboFillOfActidIarg+0xaddf1
00000000`0017d730 00000001`3f33a9ef : 00000000`0017e0a0 00000000`00000b86 00000000`00000000 00000000`0fea0000 : MSACCESS!CreateIExprSrvObj+0xf53d2
00000000`0017d790 00000001`3f33a20c : 00000000`06620400 00000000`00000000 00000000`00000001 00000000`0017e420 : MSACCESS!CreateIExprSrvObj+0xf4c4f
00000000`0017e400 00000001`3f6019cd : 0071023b`007a000a 00000000`00374a30 00000000`00000005 00000000`0000000c : MSACCESS!CreateIExprSrvObj+0xf446c
00000000`0017e850 00000000`06706fd5 : e2504700`aa00ee81 00005d1b`0f2363ea 00000000`0017e9e0 00000001`3f200000 : MSACCESS!IdsComboFillOfActidIarg+0x60ea9
00000000`0017e8f0 00000000`0a30c378 : 00000000`00000000 00000000`00000008 00000000`067069ac 00000000`00000000 : 0x6706fd5
00000000`0017e960 00000000`00000000 : 00000000`00000008 00000000`067069ac 00000000`00000000 00000000`00000008 : 0xa30c378
FOLLOWUP_IP:
ACECORE+171f36
000007fe`e3951f36 4d3927 cmp qword ptr [r15],r12
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ACECORE+171f36
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ACECORE.DLL
STACK_COMMAND: .cxr 0x171ed0 ; kb
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_80000003_ACECORE.DLL!Unknown
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/MSACCESS_EXE/15_0_4420_1017/50674523/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1
Followup: MachineOwner
5、Where the access crashed I used the ODBC trace to get the trace log of the ODBC API.
The ODBC API called by Access before it crashed are the follows.
I also ansysised the log,and I did not find any Abnormal.
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
6
SWORD
-8 <SQL_C_WCHAR>
PTR 0x00000000002C1F20 [
12] "LENGTH"
SQLLEN 62
SQLLEN * 0x00000000002C1E38 (12)
Test 1174-10f0
ENTER SQLGetData
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38
Test 1174-10f0
EXIT SQLGetData with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
10
SWORD
99 <SQL_C_DEFAULT>
PTR <unknown type>
SQLLEN 4
SQLLEN * 0x00000000002C1E38 (-1)
Test 1174-10f0
ENTER SQLFetch
HSTMT 0x0000000009F7C490
Test 1174-10f0
EXIT SQLFetch with return code 100 (SQL_NO_DATA_FOUND)
HSTMT 0x0000000009F7C490
Test 1174-10f0
ENTER SQLFreeStmt
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
Test 1174-10f0
EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 0x0000000009F7C490
UWORD
0 <SQL_CLOSE>
6、I also did the test with the Access 2010,and with the Sql Srever/Oracle.
The results are the follows.
1) With the Access 2010(X86 or X64) and Access 2013 X86,it successes when I export the table to the DB Symfoware.But only with the Access 2013 X64,the Access crashed.
2)With the Access 2010(X86 or X64) and Access 2013(X86 or X64),using the Sql Srever/Oracle,it always successes .
According to all the descrived above, I wonder if it a bug of the Access2013 .
Could anyone can help me ?
Thanks for any help.

George Zhao
Thank you for your help.
I have already install
the latest patches of the Office 2013.But it doesn't work.It is down also too. And ODBC
drive of Database Symfoware is the newest driver of the Database Symfoware. Now I wonder that
if it si a bug of the ODBC
drive of Database Symfoware,I should fix the bug,but I have analysised the odbc trace log and I do not find any wrongs ,so I think maybe it is a bug of the Access .
I have see many situations about the Access down on the internet .

Unable to open connection to MS Access 2013 .accdb file Under WCF Web Service Project Using Windows 8.1 64bit

I am encountering the following error when trying to connect to an Access 2013 database:
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
I have Visual Studio 2013 SP3 running on Windows 8.1 64bit OS which also has Office 2013 installed (which includes MS Access 2013). My project is a WCF web service using .NET Framework 4.5.1 using any cpu as target. I have tried reluctantly
to install the older drivers as described by in the below article:
https://social.msdn.microsoft.com/Forums/en-US/1d5c04c7-157f-4955-a14b-41d912d50a64/how-to-fix-error-the-microsoftaceoledb120-provider-is-not-registered-on-the-local-machine?forum=vstsdb
and also went through the "Add Data Source" wizard in the Project menu to have the connect string automatically built. Even with the automatically built connect string I can not connect to the .accdb file from within my WCF web service.
What's odd is if I use the Database Explorer in Visual Studio it has no problem connecting the my Access file. I inspected the connect string and tried to use it as well but still get the same error. Even stranger is that I have no problem connecting
to the Access DB in an ASP.NET project on the same PC. I am also able to connect to the Access file using a simple Windows Forms application. So I'm wondering if it has something to do with trying to connect to the Access file from a WCF web service
project.
What I'd like to know is if anyone has been able to get this to work in an environment as I described above as a 64bit WCF web service project? I tried to switch my project to 32bit but when I do I get a different error which reads:
System.BadImageFormatException: Could not load file or assembly 'file:
Almost to the point of trying to get this web service project done with SQL Express but would like to know if it can be done with MS Access 2013. Any information anyone can provide to help me get past this issue is greatly appreciated. Thanks.

Have you installed the 64-bit Access driver on your machine? See
Data Source Names and 64-Bit Operating Systems for the differences in odbcad32. Call %SystemRoot%\system32\odbcad32.exe to check the drivers.
How do you host your service? Stand-alone or IIS or embedded to another application? Keep in mind that IIS7 runs it in its application pool which is defaullt 64bit. Thus the bad image exception, when compiling your service as 32bit.
When you need the Access database for your service to store informtation, then I would switch to SQL Server (Express) or XML files depending on your actual needs.
Also check whether your account under which your service is run has the necessary NTFS file permissions on the access file and the folder. This is getting even more complex when it's a remote folder.

Data Model damaged, Cannot connect to Access 2013 from within Excel 2013

Hello,
Recently I am not able to use PowerPivot for Excel 2013 and I cannot connect to my Access 2013 database tables from within Excel 2013. Whenever I try to click on a slicer in my Excel worksheet, it gives me the following error: "Excel was unable to load
a necessary component. This component might have been damaged or deleted. Reinstall the client software or data source driver software for your database."
I am using Microsoft Office Pro Plus 2013 on Windows 7, 64-bit version. I have tried reinstalling Microsoft SQL Compact Edition 2005 and reinstalling Office 2013. I have run out of ideas and am a loss what to do next ?
Can anyone help point in the right direction for a possible solution to this problem ???
Would appreciate all help.
Thank you.
~Maneesh
The problem with being punctual is, there's nobody there to appreciate it !!!

Hi
This is the forum to discuss questions about apps for office develop. For your question is more about Excel, I will move this thread to the TechNet forum for
Excel
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly
can either share their knowledge or learn from your interaction with us.
Thank you for your understanding.
Best Regards
Lan
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Office 2013 updates fail on computers with Access 2013 installed

I have about 10 workstations with the combination of Windows 7 enterprise 32 bit, Access 2013 and Office 2007 installed.
SCCM offers up both Office 2007 and Office 2013 updates to these machines, but the Office 2013 updates, fail to install.
The same thing happens when I go to Microsoft updates and manually install the required Office 2013 updates.
I read that one of the updates required Office 2013 sp1.
But when I downloaded it, it won't install: KB2817430 "The expected version of this product was not found on the system."
This is the second month I've had the failures. I removed KB2878316 and KB2889927 from my deployments and packages to stop repeated install attempts.
But this month I've got a new on failing, KB2899493.
Is there a way around this problem?

Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
from http://support.microsoft.com/kb/2784668
When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
version of Access again.
Is this likely to also apply even when running App-V?

Questions about the future directions of InfoPath and Microsoft Access

Because I have been confused about the future directions of InfoPath and Access, I wrote a short blog post, which I have pasted below. My question is, can Microsoft provide some more guidance on Access vs InfoPath? If Access is indeed the
the future direction, can you please provide some pointers to resources that can help us transition.
A Short Review of MS Access, SharePoint ,InfoPath (2013)
After the November 2012 SharePoint Conference in Las Vegas (#spc12) there were a number of blog posts and people saying that Access 2013 was great and would be replacing InfoPath.
Marc Anderson and
Ruven
Gotz have short posts summarizing #SPC12 and touch on the subject of InfoPath and Access. I also spoke with several individuals shortly after #SPC12 and they were excited about Access 2013.
Since I rely heavily on InfoPath for much of what I do, I wanted to kick the tires and see what everyone was talking about. First, a few notes about SharePoint 2013 and Office 2013.
Microsoft should rename Access: If you have tried to
bing the word Access, then you know that the search results are overwhelming, because the word "access" is used for so many other purposes.
Use the RTM version of Office 2013! I was performing my investigations by leveraging the Office 365 Beta and the Office Applications that come with it. Not much was working! After I uninstalled the Beta
version of Office 2013 and Installed the RTM version everything seemed to work.
Windows 7 and IE 9.0: The drag & drop that is being touted as
"manna from heaven" seems to work well with Firefox, Safari, Chrome, and IE 10, but it does
not work with IE 9!
Non Microsoft browsers are still second class citizens (except for the drag & drop): Microsoft has finally done away with the Active X's for datasheet view (that is brilliant!) One can now see the newly
minted datasheet view in many browsers. But I still find that one needs to be in IE to do a number of key manual opeartions. For example pasting numerous rows of data from a spreadsheet into the new sheet view works only in IE.
Access 2013
Microsoft Access is touted as a non developer tool. I know a number of people who are on the business side and love Access. These people will like the renewed energy that Microsoft has applied to Access. One should note that conceptually
this functionality existed in SharePoint 2010. Here is what I see that is new:
+The new version works better:Although I haven't tested it fully, it seems that many more features that work on the Desktop version of Access, now work in the published Web Application which is hosted by SharePoint 2013.
+The new version has fairly robust browser based forms: End users can now fill in data using forms that are rendered in the browser.
+The published version that resides in SharePoint now uses its own SQL server tables. So the engine appears to be SQL Server, not a modified version of Access built for a server. This stands to be quite robust, but I imagine
that some quirks will surface due to new model.
The limitations are:
- Access is pretty much its own application and does not integrate with SharePoint building blocks. For example, an Access table is not easy to integrate with a SharePoint workflow. Further, although Access forms now are visible
in a browser, they are not nearly as rich as InfoPath forms. InfoPath forms cannot easily integrate with the Access tables. In order to integrate SharePoint features and Access, one needs to tie SharePoint list(s) to Access as data sources.
This overcomplicates the model and one may very well run into synchronization issues.
In short, although I believe there will be some people who will be happy with newly minted Access, I do not think that Access will be able to replace InfoPath and Workflow technologies. I do agree that Microsoft does not seem to have put much energy into
InfoPath. If they leave a vacuum in this space, then others may very well take over, for instance Nintex Forms.

Although I agree with the comments made by Ruven and Marc after the conference please note that those blog posts are their own personal opinions and that they don't work for Microsoft. A lot of people have asked Microsoft to clarify the future of InfoPath
and the response up until now has been a deafening silence. In my opinion speculations about Access replacing InfoPath are premature.
I should also point out that most of your comments about Access 2013 above are actually about Access Services in SharePoint Server 2013. Access Services are NOT Access they are a shared service offering in SharePoint that convert and publish Access
databases and forms. As you point out once an Access database is published through Access services it is converted to SQL Server and no longer resides in Access. Of course I don't work for Microsoft either so these are all just my personal opinion.
Having said that I doubt you will get the confirmation/response that you are hoping for from any official Microsoft channel.
Paul Stork SharePoint Server
MVP Principal Solutions Architect: BlueChip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Import MS Access 2013 tables into SQL Server 2012

Hi there,
Is there a step by step example somewhere showing how to import an MS Access 2013 table into SQL Server 2012?
I have read the existing posts and don't see a definitive answer.
I have installed MS Access 2010 engine, first 32 bit then 64 bit.
I have installed the MS Access 2013 runtime on my server.
I use the Office 2015 Access Database Engine OLE DB Provider.
I get the error:
Error 0xc0202009: Source - APEntries [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37.
Error 0xc02020e8: Source - APEntries [1]: Opening a rowset for "`TableName`" failed. Check that the object exists in the database.
The post regarding the above errors doesn't resolve the issue.
I have full administrative permissions on the server.
What is the trick to making this work?
Thanks,
Ric
Ric Miller

Hi there,
I tried the exact same operation on a third machine.
This machine has Windows 8.1 64 bit, SQL Server 2012 64 bit, MS Office 2013 Plus 32 bit.
I am the administrator on this machine.
I installed this:
Microsoft Access Database Engine 2010 Redistributable 32 bit (because I have MS Office 2013 plus 32 bit installed.)
From here:
http://www.microsoft.com/en-us/download/details.aspx?id=13255
It won't let me install the 64 bit version without uninstalling MS Office 32 bit.
I created an MS Access database on this machine using MS Access 2013 and created a table with 3 records.
I used the "Import and Export Data (32 bit)" from the start menu.
After I installed the "Database Engine 2010 32 bit" driver above, I now have the option of "Office 2015 Access Database Engine OLE DB Provider" as Data Source which I did not have prior to doing this installation.
I selected the driver and added the Properties of the Data Source Name file location of the MS Access file. I am using a blank password.
I go thru the same sequence of selecting a table to import and after running the result is the same:
Error 0xc0202009: Source - APEntries [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37.
"Error 0xc02020e8: Source - APEntries [1]: Opening a rowset for "`TableName`" failed. Check that the object exists in the database."
This seems to be consistent across three machines with three operating systems with the same files and the same result.
I understand that some people have gotten this to work.
I would appreciate it if anyone can report an error in the above procedure to me.
Thanks,
Ric
Ric Miller

2012 r2 -Microsoft Exchange 2013 DNS timed out

I just installed Microsoft Exchange 2013 on my 2012 r2 server. I just installed all of the Roles &features, then I went to my fire walls and then I disabled them (temporarily). I configuring my IP addressing, DNS Ip address and a dns suffix. Now I
can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address. I can ping my IP address though. If anyone has any suggestions that would help then let me know. Thank you for any responses!

Hi Dallen,
>>Now I can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address.
It is not a hyper-v issue , it's more like a network problem .
First , I would suggest you to disable firewall in DNS server for troubleshotting .
If firewall is truned off then you still can not ping the DNS server , you may check if the exchange server can ping other IP address in your LAN to check network conectivity .
If they are in different subnet ,you may try to check the configuration of the router .
Any further information please feel free to let us know .
BestRegards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Task Bar Icon (Access 2013)

This is my first database I created from scratch in Access 2013, and I am not sure how to change my Windows Task Bar Icon use the Application Icon. Not a huge deal, but to keep consistency between my systems, it would be nice to resolve.
How does one get Access 2013 to use the Application Icon to show in the Windows Task Bar when the program is launched?

Hi Mark,
>> it wasn't a big issue, it is just by assigning an Icon in Access 2010, the application magically had that same icon on the task bar showing open programs.<<
Based on my test, the icon in Windows Task Bar will not change after I assign an icon for Access 2010. I tested in Access 2010 on Windows 7, here is the screenshot for your reference:
If you want to Access support this feature, I suggest that you submit the feedback from link below:
Submit Feedback - Microsoft Support
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

"System Resource Exceeded" for simple select query in Access 2013

Using Access 2013 32-bit on a Windows Server 2008 R2 Enterprise. This computer has
8 GB of RAM.
I am getting:
"System Resource Exceeded" errors in two different databases
for simple queries like:
SELECT FROM .... GROUP BY ...
UPDATE... SET ... WHERE ...
I compacted the databases several times, no result. One database size is approx 1 GB, the other one is approx. 600 MB.
I didn't have any problems in Office 2010
so I had to revert to this version.
Please advise.
Regards,
M.R.

Hi Greg. I too am running Access on an RDP server. Checking Task Manager, I can see many copies of MSACCESS running in the process list, from all users on the server. We typically have 40-60 users on that server. I am only changing the Processor Affinity
for MY copy, and only when I run into this problem. Restarting Access daily, I always get back to multi-processor mode soon thereafter.
As this problem only seems to happen on very large Access table updates, and as there are only three of us performing those kind of updates, we have good control on who might want to change the affinity setting to solve this problem. However, I
understand that in other environments this might not be a good solution. In my case, we have 16 processors on the server, so I always take #1, my co-worker here in the US always takes #2, etc. This works for us, and I am only describing it here in case it
works for someone else.
The big question in my mind is what multi-threading methods are employed by Microsoft for Access that would cause this problem for very large datasets. Processing time for an update query on, say, 2 million records is massively improved by going down
to 1 processor. The problem is easily reproduced, and so far I have not seen it in Excel even when working with very large worksheets. Also have not seen it in MS SQL. It is just happening in Access.

Microsoft Access 2013

Similar Messages

Maybe you are looking for