Hi all, I have created a database for work in Access2003. I have two questions. The first is, many people at the work place use AC97 and some use AC2000. In order for everyone to use the database, i have saved it in AC97 format. It seems to open fine in Ver2000 and 2003, but i get this nag screen on load up with these versions saying "do you wish to convert the database". As I'm working off a shared drive, i don't really want anyone converting the dbase. Is there a way to disable this nag screen when loading in AC2000 and AC2003??
Second question, is it possible to have more than one instance of the database open at anytime? . If I've got the database open, my colleague can't open it. Its a simple database that writes records directly to a table. Thanks for any advice.
My office is running Microsoft Access 97 but I use voice recognition software and that is not a real compatible with the 97. I need to upgrade to the latest Microsoft Access version.
My question is if I upgrade to Microsoft Access 2003 is there a way for my created databases to be saved so the users of Microsoft Access 97 will be able to open and use the database? I understand they will not be able to make any changes to the database but will they be able to open it/view it entered their criteria into the queries can be able to see their information?
I have an Access db that is going to be shared by two different users. One user has Access 2003 and the other has Access 2002. Will there be any problems using this setup if both the users are accessing the MDB file at the same time?
I have a 2007 db, been working no it in 2007 and occasionally in 2010, careful not to use any 2010 items. Well I goofed and added a Navigation Form (2010 only) and then deleted it. Now My 2007 db opens in 2007 fine, everything works, but the glowering Warning message and lovely yellow yield sign show up constantly. How do you resolve the incompatible items and clear this warning?
I have two questions related to deplying an Access project I have been working on.
1. I started developing the project in Access 2000, but midway upgraded to Office 2003 and so the remainder of the project has been developed in Access 2003. Things seem to be fine, except that in the top most title bar, after the project name, there appears the following text:
xxxxx: Database (Access 2000 file format)
where xxxx is the name of the .mdb file.
Why is this appearing and should I have done something or do something to make it a Access 2003 format?
2. I am at the point of deplying the db to a small group of users (about 5). Some of them may have Access 2000 or Access 2002. Should I be doing something in particular to make sure things work in their machines. Any pointers to what may be problems or what I should do will be much appreciated.
Hello, Is it possible to install two versions of MS Access on the same O.S. I already have Access97 installed. Now I want to install access 2003 without it up removing my previous access 97. If it removes/upgardes access 97 to access 2003 I will not be able to open my access 97 database. Is this possible? and if so how?
My office has updated to Microsoft Access 2007, but one of the third party softwares used requires a previous version of Access. A result of switching between the 3rd party software and Access 2007, is that 2007 installs every time.
Is there any work around to over come this problem?
Hello, Is it possible to install two versions of MS Access on the same O.S. I already have Access97 installed. Now I want to install access 2003 without it up removing my previous access 97. If it removes/upgardes access 97 to access 2003 I will not be able to open my access 97 database. Is this possible? and if so how?
I've been hired to clean up and convert a flat filemaker database into access 2003 and I've spent the last two weeks learning the ins and outs of access and doing preparations. Well, today some high up database guy in another department told me not to use access because in the future when a new version of access comes out we will have to recreate the database from scratch because there are lots of problems converting between versions. I'm aware there might be some hiccups but I don't really agree with him. Plus once the database is up and functioning I don't see why we'd even have to upgrade it to a new version. It's just a small health centre patient database with info about patients and their treatments. Does anyone have any opinions about this. Thanks.
Hi, this problem came out of nowhere but looks like it's here to stay.
Our Access app generates various Access Reports. Recently we installed a new version of our access app and since that version onwards, all pc's with Office XP/2003 print reports in black & white. Printing to PDF works fine though.
We can't find the reason for this. Which mean we had to go to all our clients to downgrade them from office XP/2003 to 2000!
Is there a way to make access be able to store software versions and product keys automatically? Programs I am most interested in is like Microsoft Office suites and Adobe Acrobat and Photoshop and whatnot like that. I am not sure if this is even possible but I am trying to get my database fully functional with all the data and efficiency I can for at least 5 people so that I can try to sell access as a better tool than the service they are using now.
my post at www.thescripts.com was deleted. It seems they don't really want a true deployment solution help to all ms access developer.
Ms access is a true king RAD DB frontend dev't. tool but the deployment of the finish apps are very unstable.
Sagekey is almost there, but I want to make a single EXE on my Access Apps that run even on the usb flash disk.
I have already found the solution, perfectly done! using one of the tools available in the web. but I will not post it again, I'm afraid this post will be deleted again... I hope this forum truly helps.
I have problem concerning the compatibility of the access applications that I am working on, when save my work in my computer, I make a copy to another computer, there appears an error in the execution of a button click or others, I have checked all most every thing related to the correctness of the code and path of the database file, they identical. the following attachment, the image that shows the message as it exactly printed.
If I were to create an Access database within the Windows platfiorm, would it be accessible on a Mac machine with MS Office for Mac installed? Please advise on the implications here i.e. will the Security features work (MDW file, etc).
I've been working on a database at work in Access 2003. I need to speed up though, so I thought I'd it bring it home on a USB memory stick and work on it here using Access 2007. I do this all the time with Word and Excel files and just take care to save them in 2003 version so I can use them back in the office.
But when I try to open this database, it's asking for a password. I know for a fact I haven't set any password on it, because I wouldn't know how to. Holding down the shift key is ineffective too.
Is Access 2007 not backwards compatible or something?
I created an access 2010 file containing tables and 2 linked forms to distribute to different people so that they can enter data for a project. The problem I am having is that the people receiving the file aren't able to open it, different error messages pop up:
-accessde.dll missing or -vba6mtrt.dll missing
Is there a way to export the access file so that regardless of the program, they are able to open the file? if not, what are the solutions to this?
Should be a quick and easy question here... I'm getting close to splitting a DB. Back end mbd, front end mde. Searched the forum and a few other places. One subject didnt seem too clear... I developed the db in access 2002, a few of our computers are running 2003. Will I run into any problems with this setup??
Hello, I wrote an access program using version 2000 and the activex calendar 11.0 which came with the software. When i tried to run the same program on access 2003 none of my dates worked and I got error messages all over the place. Help!
Hi I am trying to find the best way to synchronise several different versions of the one database, two of which are used by remote users so i can't really set one database on a central server, I am trying to come up with an as automated a process as possible as it will need to be done on a regular basis, has anyone any ideas??
it is a microsoft access 97 database
I will be updating it to a newer version as soon as possible
I have a database in Access 2007 - 2010 that I push out to a couple of different co-wokers.One of my co-workers is using MS Office 2013 and the buttons I have on the forms and reports look inflated.Is there anyway to prevent this in Design mode so what I see in my version is the same as the new version of Access?
I keep the production version of my database on a server, and a copy of it for development work on my desktop. Today I've made several changes to the development version, which didn't work. I then opened the production version held on the server in a separate MS Access window to compare the queries/results to see where the problem was and have found that the changes have automatically updated in the production version. Can anyone explain this? They shouldnt be linked at all. The 2 versions both link to a datawarehouse through an ODBC link, but shouldn't be linking to each other (I'm using Access 2003).
I have been asked to add features (and fields) to an existing database containing private medical data. The idea is to add features to the empty database, test it with fake data, purge the fake data and deliver it to the user in another state with a simple update button. The Access 2010 database is in one piece (No front/back end).
I am looking for the best/shortest VBA method to move a lot of preexisting field data from the old database to the new version. I think I have it mostly figured out; I have code for counting, reading and writing the table names, field names and field data.
However, because the data types vary within the tables and there will be new fields in the new versions tables, my only idea, so far, is to code through the data table-by-table and field-by-field, a lengthy process with a large footprint. Moving entire tables or complete records may not be effective. Any faster way to transfer all these tables field data?
