Access 2007 / Moving Database To Another Computer?
Nov 18, 2011
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?
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
I have a search form built that depending on the dropdown selection on the form, it will run a query to SQL Server 2008 and provide data. There are 5 SQL Server db's so there are 5 different queries. I have each SQL Server linked to the Access DB. When I moved to someones else's computer I got a ODBC Call Failed message. In order to fix this, I had to recreate the links on that person's machine, then change the SQL code in the query with the new name of the linked DB.
I have a database built using Microsoft Access 97-SR2. I want to copy it to another computer (my office computer). I was successful in burning the file to a CD-R disc. However, when I run the database from the disc, a message appears saying its READ ONLY-it apparently makes it Read Only automatically. I want to be able to change and edit the data and the controls, ie. forms, reports, etc. on the other computer. How can I transfer the database my other computer, without it becoming Read Only?
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)
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?
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
Greeting All, I am trying the beta version of Access 2007 and realize that when converting Access 97 to Access 2007, the new db in Access 2007 has an extension of .accdb. I rename the db file name to xxxxx.mdb and the VB app fails to recognize it.
Is there any way to convert the xxxx.accdb (Access 2007 beta) to xxxx.mdb so that I can try my app against the Access 2007 db?????
I am kinda new to 2007 and have at the moment a simple database.
I want three things
A: Use the database on a server.
B: Restrict the use to users etc as i used to be a ble to do in Access 97 i think (do i have to make a MDW if so how ?) 9I tried ACCDE but does not seem to do anything)
C: When users use the datavase not see all the normal access editing stuf..
Just upgraded to Acccess 2007 and have ownership problem extracting queries from a 2002 db.
When trying to import into a new 2007 or export from the 2002, get "you have no permission" message
Have created a new user tried to change owner of the db, but no permission File security looks correct in that I am owner of the file with full permissions, but Access doesn't recognize me as the owner
Tried logging in as admin, but it isn't the owner either
This is not critical, just very time consuming, this is a test project, but it would be nice not to have to rewrite about 30-40 queries and equivalent forms
I am not sure where to post this question. I remember finding a forum just for Microsoft Access 2007 questions, but I couldn't find it again... Indifferent
Anyway, I have created a database, and have been testing it with my application. I have some data in this database. I was wondering if there was a way in Microsoft Access 2007 to create an empty copy of the database for release. In other words, I would like to create a copy of the database with all of the tables and columns, but without the data (rows) that I had entered as part of using my testing database...
Does anyone know if I can do this?
If anyone knows where this Access 2007 forum is, or resources that might answer my question, please let me know, as I would greatly appreciate that.
I have created a database in Access 2010 and I am not able to open the same database in Access 2007. I have read somewhere that it is possible to open. I get the message, " Unrecognized database format". In Access options, the default file format is, "Access 2007".
I am building a database of all the computers at the company i work for. Each computer has a unique ID. I want to be able to enter the ID of a computer and have its details displayed. IE. A user enters 34321 and then computer 34321 shows up and has information about its history specification etc.
I'm using Access 2007, with what I think is a normal database that I've built up over the past month (maybe 15 tables, <1000 records, 20 queries, 4 or 5 reports and macros). I'm not an experienced Access programmer, so I don't think I'm doing anything fancy with security settings or any other such stuff. (If I have, it's surely by accident, not by intent.)
When I try to back up the db using the simple office button -> manage -> backup method, access generates a date-stamped backup filename and opens a file save dialog for me, but it ALWAYS fails to backup the database. I always get the same error message when I click save, whether I save on my machine, or on a network drive.
"Could not use '<path to the current database dir><backname>.accdb; file already in use."
This same error occurs when I create a new blank database with a single Table1 in it, so I don't think it's my database.
Does anyone have any idea why this might be happening? I scoured the net for help, but nothing. I checked various Access forums, but nothing. So I arrive here after I've done my homework... thanks
I want to hide the top toolbars when my users open my database in Access 2007! i have an autoexec macro to maximise the window which gets rid of the navigation bar on the side but cant work out how to hide the top bar? do i need to write code? if so what code and where would i input it.. any help would be much appreciated...
I am on a deadline today and when I went to open an Access 2007 (I abhor the fact that I am forced to use 2007) database, it will not open. It gives me the error message Unrecognized database format [file path].
I have tried creating a brand new database and importing all objects from old to new but I get the same error message.
employee personal recordemployee job statusleave recordinventory record issue to employeejob performanceinventory control of equipmentforms, queries, tables, login forms.
I work with an Access 2007 database that I split into a front end and back end. The back end holds all of the tables and the front end holds the queries, forms and reports. It is also a multi-user database, in that we have 14 people having access to the same back end. Each of the 14 people have their own front end. I have one main table in the back end listing clients and their individual ID numbers. That table has a One to Many relationship with several other tables, such as Case Notes and Authorizations, to name a couple.
Here's one of my problems: Sometimes data that is entered by a user will disappear.
Example 1: User creates a new record in the Authorizations form. Sometimes it is created by duplicating an existing record, sometimes it is completely new. User then prints a report from that new record, which looks like it has been saved. A couple minutes later, or a couple hours later, or maybe even the next day, user goes back into the database and cannot find the record that was previously created. At that time I look in the back end and cannot find the record either.
Example 2: User creates a new record in the Case Notes form on Day 1. These are always completely new records. User returns to the database on Day 2 and the new record sometimes does not show up in the form or in the back end table.
I cannot MAKE these things happen and they are sporadic, which makes it hard to diagnose, but why this was happening or if there was a way to retrieve the lost data.
"how to COMPACT the DB by introducing delay of 10 seconds and then close the DB".In the Database, I'm able to accomplish the "Compact" the database using the function below.
Function Compact() SendKeys "%(FMC)", False End Function
As my DB is quite huge, the Compact action takes around 10 seconds to complete.Now, i would like to Close the Database after Compacting the DB. I tried including "DoCmd.Quit" in the function. The commands in the function, closes the DB but the Compact function doesn't seem to have executed as it needs 10 seconds to complete.
Function Compact() SendKeys "%(FMC)", False DoCmd.Quit End Function
how to introduce this delay of 10 seconds and then close the DB.
I have a standard shared Access DB application (i.e. central BE on the network, multiple users running their own copy of the FE on their local machine) Has been in production for a while, no major issues.
New user has been added in recent weeks. My error logger has picked up an error he hit earlier today - doesn't appear to have been fatal (he hasn't come to me with a problem, suggesting he just "OK"d the error prompt and continued on - I need to confirm this with him though...)
Error was 3343 "Unrecognized database format 'C:TempMyDBMyDB.accde'."
Can see it was tripped on a particular form which queries certain data into a subform (so he was obviously able to open the FE and connect to the BE fine; it was several steps down the road where the error has occurred).
Using Access 2007, can I return a value for CurrentProject.FileFormat WITHOUT opening the database?
I'm looking for a way to determine the file version of a given Access database without actually "opening" the database in Access (I don't want it to ever be visible at all or in any way).
So to open a database in Access 2007 "without opening it," I'm using:
Code: Dim db As DAO.Database Set db = DBEngine.Workspaces(0).OpenDatabase("C:Path-ToFile.accdb")
From here, there are at least two different "version" indicators that can be used, as in this example:
Now, if you run this code on an Access 2002/2003 .MDB file, you will get:
Code: 4.0 09.50
If you run this code on an Access 2007 .ACCDB file, you get:
Code: 12.0 09.50
Note two important factors:The db.Properties("Version") seems to be returning the JET version from what I can see in research. This is NOT what I'm after.
The db.Properties("AccessVersion") returns THE SAME VALUE for an '07 ACCDB as it does for an '02-'03 MDB, since Microsoft never updated it, apparently.
Now.... the one way that I have found that ACCURATELY describes the version of a given access database file is to use:
Code: Debug.Print CurrentProject.FileFormat
...as this will always return, for example, 2.0 for an Access 2.0 .MDB file; 10 for an Access 2002/03 .MDB file; and 12 for and Access 2007 .ACCDB file (and there are others; these are AcFileFormat bitmask constants as described in Access support).
BUT, this CurrentProject object doesn't seem to be available (so far as I can see) when using the "open without opening" method described above.
SO, is there any way to return the FileFormat value without opening the database visibly? (Merely basing it in the extension isn't right either.... that would be easy but not accurate as several formats use MDB.
