So I have created 2 Linked tables based on lists that exist on a SharePoint 2007 site ( Institutions & Survey ). The 2 lists are linked through a look up field in the Survey list that reference the Name field from Institutions.
After creating the Survey table in my Access 2010 database (.accdb) I notice that the lookup field that links the 2 lists together isn't present in the table. To make matters worse, there is another field ( _EncodedAbsoluteURL ) that I had deleted before but is present in the table, but this is only visible in Design view, in the Datasheet view it's nowhere to be found..
When I look at the table in Design view, I can even see a field called Title1 that isn't shown in the Datasheet view nor can I find it on SharePoint, just like the field I mentioned before.
I have also tried to recreate this scenario with 2 simple lists that are connected in the same way but this works perfectly.
Since you can see the column in the design view it means it has been imported just it is not visible in the datasheet view. That is because these columns are hidden in access. Access hides some columns by default.
You just have to right click on the header of any field and click on unhide. You get a list of all the fields from the SharePoint list. You want to show select the fields you want to display and close it.
Now you can see the columns. Hope this solves it.
I have been able to resolve the issue using the answer posted here: https://sharepoint.stackexchange.com/questions/117707/access-linked-to-sharepoint-list-is-missing-fields/145501#145501?newreg=2c19852039b04d48b93539d39773044d
The problem was caused due to caching of data so if you clear your cache after deleting the table and then restart your DB the issue should be resolved.
Related
I have an absurd problem when I try to copy table from one Database to another.
Say I have a database with table containing drop-down list for all its records.
Not sure if it matters, but the table is populated with data submitted by users via Excel macro. When the user submits the record, it's pushed to this Database with attributes chosen by the user from drop-down cells.
The problem:
When I copy and paste this table from source data into other database, all attributes are missing. This is how the table looks in source data. And this is how this table looks after its pasted in another database. When pasting, I choose structure and data option.
I don't even know where to begin fixing it and why it happens. What's strange, it worked just fine couple of days ago and old submits are pasted correctly.
Your database has a relationship built between the Profiles table and the Attributes table. You should be able to see this by clicking on the Relationships button in the Database Tools menu.
By the looks of it your Profiles.ID field will be related to an Attributes.ProfileID field (i.e. the Profiles.ID field is listed in all related records in the Attributes table).
Your newly copied Profiles data doesn't have any related data in the Attributes table. When you copy that data over your table should appear as expected - with the little + icon revealing the related records.
Hello I have a pretty intricate Access database. I just jumped on this project and have never used Access. I have a form that is generating a value entry popup when I try to run it and it shouldn't be. The problem is the form is trying to access a column of a table which has been changed recently. I just have no idea where to find the query or what exactly is trying to access that column. Any help greatly appreciated. I am using Access 2016 also.
Sounds to me like the problem inst actually your form but the query your form is based upon.
This may be a separate query or a query built in your forms record source.
Go to your form in design view. Open up the property sheet. (Under design tab) make sure the dropdown box has Form Selected and look at the Record Source.
The record source may state a query name, In which case you should remove the field/replace the field with another in that query.
Or if it says something along the lines of "Select ......" then just alter that query to not have the field you have removed/renamed and the problem should go away.
However it is worth noting that if you have sub forms it could be the record source of one of those.
I am sincerely sorry if this question has been asked before, however with my limited knowledge of using Microsoft Access forms I am having an issue that is likely a very simple fix.
At the moment I am trying to create a form that will allow me to post data into an intersection table using combo boxes, the purpose is to create a relation between Clients and Project Numbers, these are intended on being a Many-to-Many relationship.
Relation Example
To begin with one issue I am running into is that when I use the intersection table to select a unique Client Name I get multiple entries from the drop down menu when there are multiple items in the intersecting table.
Form Example
The second part of my issue is that I am unsure how to post data to the intersecting table once the dropdown selections have been made.
Any help is greatly appreciated, and I thank everyone for their time.
The first part is to create a form in which you find, and edit data in the main client table.
This form will ONLY be based on the single main client table.
You perhaps ALREADY have a nice form to edit the client table anyway. I mean, how else will users find and edit a client anyway? So this issue and problem will LONG be dealt with before you do anything else of use in the application.
The form based on this single table might look like this:
Ok, now close the above, and create a second form to allow adding some choices of favorite colors (or in your case ClientContract). So the form will be based on this child table.
Again, like the first form, this form is based on ONE table.
Make this form continues, so click on ClientContract table, and then from ribbon choose multiple items form from the ribbon. It will look like this:
Of course we don’t want the user to have to manually type in the color (or project in your case), so we drop in a combo box from the ribbon and use the wizard. MAKE sure the first column of this combo is the PK of the ProjectNumber table, but FOR EASE of reading and selection, include ProjectNumber and Project Description columns in that comb box. NOTE in above how I also had added that combo box.
Assuming you closed and saved this form.
Now open our first main client form in design mode, and drag + drop in the continues second form we just created onto this form. The resulting form will look like this:
Access will automatic set up he customer_ID for us (because it is a sub form attached to the main form that only displays the one main record).
Once the above works, then again close the lot, and open up our continues form in design mode and remove all the extra junk.
(leaving ONLY the combo box).
The result is this:
I'm building a risk and issues tracker and have become stuck after some good initial progress. I'll explain my setup now.
Tables
A table containing all open projects
A table containing all open
risks and issues
Relationships
A one-to-many relationship between with project ID (Primary Key in the project table) to the risks and issues table
Queries
A query that will filter results from the projects table that have been selected in a combo box
Forms
One form containing a combobox that allows the user to select a project. There is also a text box, which will be populated based on the selected project. The text box is populated using DLookUp on the above query, and I have chosen a field to be populated from that. This all works fine.
I am able to select a project and see a little information about it using the above set up. The next step for me is to be able to add a risk or an issue.
What I would like to happen is to have a create Risk / Issue button, which will pull across the Project ID (primary key) from the selected project, and add a new record in the **risks and issues* table. I will also need to add in additional information about the risk, dates, owner etc.
Also, by having the project primary key tied to each risk, I should be able to pull in any additional info about the project that I require.
I can write more if required - I'm not really sure which information is needed. Also, the form 'sits on' my projects table which could well have been the wrong way of doing things, however I still don't know how to bring in the data from two different tables.
I appreciate any effort and patience put towards this.
From my understanding of the question it sounds like your trying to update your risks and issues table with a single form that is bound to your projects table. If you're adding a record to risk issue table with a bound form it needs to be bound to that table.
My best answer would be to start fresh with a new form created by the wizard.
Make sure you have all the fields you want in your form in the risks and issues table.
Create a form based on this table using the wizard.
Change the Project ID control to a combobox by right clicking and selecting change to, combobox.
Set the row source to take project id and project from the project table and then make sure project id is the bound field and project is the displayed field(by adjusting column widths and bound column properties).
After doing this you should have a form that updates your risk and issues table while selecting the project from your project table. If this is not what you were asking or you wanted to do it a different way let me know I'll see if I can help.
So I have a custom list in SharePoint 2010 with 10 or so columns. I then link the list within MS Access 2007. Works just fine until I try adding a look-up or people-type column to the list, then the next time I refresh the MS Access table link I get the following message:
Error: "The Microsoft datbase engine cannot find the object 'TMP%.MAU#'. Make sure the object exists..." blah, blah, blah
Then of course, the data is inaccessible through MS Access after that point. If I then go back to SharePoint and delete the new column, it starts working again in MS Access.
I can add any other kind of columns, and it works fine.
What gives? Is there s limit to the number of people columns you can have in an MS Access linked SharePoint List?
========
New Information
So I deleted all of the data from the sharepoint list, and the error went away, no matter how many people columns I added. But as soon as you add a single record back in, the error returns... :(
Found the solution.
The error stems from a "hidden" threshold limit set within SharePoint Central Administration that limits the number of lookup columns returned within a given query. This means linked MS Access lists to SharePoint would be limited as well, hence the error. The problem is MS Access 2007 doesn't give you a nice error message to explain this to you, whereas SharePoint 2010 does.
The fix is simple--just bump up the threshold and you're good to go. Here is how: enter link description here
This does work in Access 2010.
I suspect you need thus Access 2010 use such a multi-value type of column. While 2007 does support SharePoint, I thinking this is a new type of column in SharePoint.
When you say you are adding a people type, then I assume you are choosing "Person or Group" as a SharePoint type. You are then setting this column as multiple choice.
This does work just fine for me in Access 2010. Even in table edit view from the Access side I get the multi-choice pick list, so I am thinking this is an Access 2007 limitation. Note that I do NOT need delete + re-link to see the changes after I add the new column. I did however right click on the table in Access, then choose more options, and then then refresh list. I get this view inside of access when I use that column:
I also find I can add new columns from inside of Access to this linked table if you use the table tab on the ribbon. The people picker is not a legal type from the choices in Access, but adding from SharePoint does work for me.
The only thing I might be doing different from you is the table was originally created and uploaded from Access.