Need Help Moving Linked Access Database To A MSSQL Server
Dec 19, 2006
Hi,
My access database's tables are currently linked to an excel document. My question is, how do I move my database to the network? Currently when I move the the database to the network no one can open my tables because the link goes to my documents on my computer which they can't access on the network.
So how do I move the database and maintain the link between the database and my tables?
Currently I have an Access dB that was developed in A2003 but we are currently using A2010, it is accessed by multiple users that all have a frontend locally on there own networked PC's, with the backends etc on an old NT server, we are having problems with new technology accessing the NT server so it's well past time we got shut of it
We have a share on our network that has been made available to us to migrate all our NT server files to, Here's my problem, on testing the procedure I copied the database backend and .mdw file over to the share then tried to open the dB where upon i got the following error message
Cannot open microsoft Access database information file
On further investigation it seems that both the back end and the .mdw file have copied over with no content i.e filesize is 0kB, not only that the originals also seem to have had there content "deleted" a simple copy shouldn't have done this (I did have a backup btw)
I created a database in Microsoft Access and then upsized it to SQL Server afterwards.
I now need to add a new column to a table in the database. So I added the new column in SQL Server using ALTER TABLE command. This column is a foreign key which has an associated parent key in another table which contains a description of the column. e.g. Main_Table Case_ID Foreign_Key_Field_ID 1234 78
New_Foreign_Key_Table Foreign_Key_Field_ID Foreign_Key_Field_Desc 78 Describes the ID 78
I also setup a CONSTRAINTREFERENCE between the fields in these 2 tables.
I then relinked my tables using the Linked Table Manager to pick up the change to the table I altered (Main_Table). I also linked to the new table I created (New_Foreign_Key_Table).
My problem: In Access if I create a new table I can select the lookup value for a field in the Table Design view Lookup tab. However, I altered my table in SQL Server and then linked to it again to pick up the change. Now when I view the linked table in Access it does not have any lookup value AND it's not possible to change this for a linked table.
Is there some piece of SQL I can use in SQL Server to change the lookup value for the field in my table OR have I approached this the wrong way. Should I have modified the local table in Access and upsized it again?
Otherwise if I select all values from my Main_Table in a form it displays the Foreign_Key_Field_ID instead of the Foreign_Key_Field_Desc because the lookup value has not been set to Foreign_Key_Field_Desc
This posting is a bit long - I hope it makes sense.
Any ideas or suggestions would be greatly appreciated.
I have created a few split multiuser databases in Access 97 that my company has used over the past few years. Currently, we are trying to move everything to a new network server. When I did a simple copy and paste on Friday moving everything to the other server it seemed to work fine. Until I tried to open any of the databases. I kept getting the message that they all were read only.
Do I need to bring the database back together before transferring it? I also plan on converting the databases to Access 2003. What precautions should I take in doing this?
Thanks for any and all information you can pass along.
So the database I have right now is split, with the back end on our server. Everything has been going great, however there are several second time delays when loading large forms, queries, etc. I've heard that moving the back end to an sql server is the way to go for speed.All forms and queries are on front end of database. Tables are located on the back end which is sitting on the server.
I have a fe that has 5 tables linked to a backend db on the server.I want to add a new table to the fe that is linked to a second db on the server? What I have tried.I have created the tbl_called in the fe.when I right click on it and go to Linked Table Manager I do not see it on the list. The only tables in the list are the 5 I linked before. Why is tbl_called not showing up??
We are sharing an Access 2003 database amongst two departments that contains twelve (12) tables that are SQL Server linked tables. Nine (9) of the tables work just fine for people in both departments. Three (3) of the tables cannot be opened until the user refreshes the link(s) using their ODBC DSN.
We do not understand why nine of the tables work without issue but three will not.
Has anyone ever run into this issue before? Does anyone have any ideas on how to resolve this issue?
I'm using Access 2007 which I built a database that runs queries off of tables using ODBC. The database is all done in ms access, I've used no visual basic programing on it. I'm now trying to move a copy of the database to another computer's local drive in the office. When we try to open it on the other computer it gives me an error that says "There was a problem sending the command to the program" and Access hangs, which I then have to run task manager to end the program.
Specs Are: Windows 7 64bit (the db was created on Windows 7 32bit)
Moving to new computer, both under Win XP pro, Access 2003. New computer is MacBook Air running Parallels. Transferred Access database via an external hard drive. Now the data shows up as Read Only. Is there a procedure to run down the cause and make the data accessible?
I have an MS Access accdb with linked SQL Server 2012 ODBC tables. I am working on a procedure to copy data from local tables to these linked tables (identical schema). I did a simple
Code:
DoCmd.RunSQL "INSERT INTO linkedTable SELECT * FROM localTable"
This works, but is very slow. Way too slow. (INSERT copies the data one record at a time).
I would like to copy the data in a bulk operation, or operations that I can execute programmatically.
I have an Access database on my server. My client does not like the idea of having to download the db, make changes, then upload it back. In the past, he has dealt with SQL databases, where you can create an access data project, that will give you a desktop shortcut straight to the database. I was wondering if there was any way to do something similar with an Access database. There is FTP setup for the site and all required permissions are setup. Is there any way to create a desktop shortcut, so he can edit the database in real-time, without having to download and upload? Thanks for any help.
I have a database with a couple of search forms to use for my company. My boss wants me to place this on the intranet so anyone can use it not only those with MS Access, which many people do not have on their computers. Please let me know if there is a way to do this and still make it interactive by means of searching. Thanks
I'll try to explain what I'm trying to do. I want to use the MS Access (2010) application residing on the remote server on a Access database(accdb) that is located on my local (home) PC. I copied the database from the server. How do I get Access (running on the server) to work on my copy of the database?
I tried using my local (on my PC) copy of MS Access (2007) to work on the database, but but I get file errors (file paths look like server paths).
I am rebuilding an application for a client and I have an Access table that I am using as a temporary table. Once the user is done entering information into the temporary table through a form, the user presses an update button that appends the records using an Append Query in Access to an SQL Server Table.
The following error message occurs:
"ODBC -- insert on a linked table 'linked tblname' failed.
[Microsoft][ODBC SQL Server Driver][SQL Server] Explicit value must be specified for identity column in table 'linked tblname' when IDENTITY INSERT is set to ON. (#545)
I am using a form, subform combination to record a bill with many details. The bill summary is posted into a tbl_TransactionsMain table in SQL Server using the ADO AddNew method. The PK for the tbl_TransactionsMain is then entered into the temporary table in Access. When the temporary table records are appended into tbl_TransactionDetail the error message occurs.
What is also interesting is while typing out this post I thought to test the error by manually trying to run the query. The query worked like a charm! :confused: When the orginal error occurred off of the form I tried to run the query manually and it failed. I am guessing that this might have something to do with the ODBC timeout.
I think SQL Server/ODBC connection is not liking how I have a set of records in an Access table with foreign key numbers assigned when I am attempting to append the records. I am new to SQL Server and any ideas are most appreciated! :)
I am currently working on an application where I am using MS access as my FE and working with linked tables to SQL server BE. I also have a few temp tables within Access that are not linked but needed.
1. What are my steps into making this into a SPLIT DB? I am assume the BE will have my linked tables from SQL and the FE will have my temp tables and forms. Is this correct? 2. Once I split it, then I can make an .ACCDE file for a Mulit User environment, is this correct?
I am finishing an Access database for a customer that may want, in a later stage, to have a website(probably ASP) that would connect on the same database. Is that possible? I mean can an Access project on a pc connect to remote database(mdb or SQL server) used by the website?
If so can you give me some quick steps to do so or a good article on it?
I have converted desktop Access database to SQL server. A medium sized app with 24 tables, 60 or so forms/subforms and about 120 queries. I created 2 split files, one containing the tables, and the other containing forms, queries, vba modules. I migrated the tables to SQL server using SSMA, and built an odbc connection for my front end. It works, except it is painfully slow. Its cos most of the recordsets that drive my front end are query based. And in many instances the queries are comprised of queries, not just tables.
Should i be creating my queries on the SQL server? Is that what people do when using Access front end with SQL server back end? Do away with Access queries? Or does the problem lie elsewhere? How do i network optimise my Access FE / SQL server BE?
I am trying to upsize the access database to sql server ,i have an odbc connection and when I try to move the tables,all the data is moving except one table "tblproductinfo" . I have attached the table data and error.
I have a database which is now reasonably finished and am looking slightly ahead at how it can be accessed by the staff. The first clinic has two stations that need constant access to it, namely the clinic area and the reception area.The second clinic is about 3 kilometers distance away from the main clinic and will also need constant access which, I presume,would be by hosting the database on a Windows based Server, to which all three locations would connect and then be able to use the database directly. When I say Windows Server I mean as could be used to host a web site on the Internet rather than use of an internal Intranet system.
Should I split the database and only host the backend part on the server (i.e. the tables)?Does the whole database need to be uploaded to the Windows Server?Is any other software required to make this work?I presume that I would need to introduce record locking? Is this easily done and, if so, how?
I'm working in Access 2010. I created a database that I want to post in a server on the read-only mode, so that users can not change forms or querys. How can I do this in Access 2010?
Everytime i want to make some changes to my "Testing" Database , always got somebody using it / opening it...
I am trying to create a button , the function of the button is close "Testing" access database who using it or opening it , Example : 5 users included me in a company , when I click a button , 4 of them will received a notification with close "Testing" database message , can do that ?
Is it same thing about speed and other issues to have ADP application that works with SQLserver and to have a MDB (or MDE) application that has no querys but works with sql views instead?
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
Hi all, wonder if anyone can assist me with this the SQL Server security/write (?) issue. The SQL Server Admin has created a table for our Dept. to use and via SQL Server I can get access to it using the username and password she supplied to me. I can also link to this table in Access 2002 via ODBC which is the way I am using to write to SQL server tables. I have developed an Access application to allow one of our staff to be able to write data to the SQL Server table at a click of a button, however when I open the table the 'add new record' button is greyed out, I can not add any data to the table. I explained this problem to the Admin as well as the way in which we access the table and she is certain that the problem lies in Access but i'm unsure how that can be the case.
Has anyone experienced this problem before ? Is there a fix and if so how is that implemented ?
