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.
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.
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?
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
Hi, I have been using "fSetAccessWindow (SW_HIDDEN)" in the open event of my main switchboard to hide the grey Access screen from being visible behind forms, reports, etc in this db. But when I started using a .vbs script file to launch the db, the Access window stopped being hidden. (The reason I use the script for launching is that it temporarily sets the db's security level to 1 which stops the macro security warning from coming up.) Apparently MS knows about this happening and released a technique to rectify the situation, but I don't understand their instructions. It looks like they expect one to have more understanding than I have. Could someone help me get this impliemented? Here is the article: http://support.microsoft.com/kb/167659/en-us Thanks!
Hi! This is Kishore, working on VB Project which is using MS-Access95 as backend. Now, i want to change the Database login Password. Could anyone guide me in this context.
Using Access's User and Group Accounts or Using a Login Form to access database?
I've been researching on how to make a database secure. How to create User and Group Accounts on access, I see the step by step instructions and tried it out myself.
I also saw some sites where they give an example of a Login Form and how to create one.
My question is do you need to create both. First create the users and groups to permit or deny access to certain forms and then have a login form?
But would that mean that they'd have to login twice? Once when the database opens because it activates the db security that was created and then login again in the login form that was created?
Also when the user logins in and clicks on the cmd button on the form which opens up another from, frmWorkLog, I have an Employee field. This field I want it to have the user's name entered automatically and "locked". So that info, employee name, is extracted from the user's login. So then the user can only see his or her records only and no one elses.
How would I go about creating that. Hope I made my explanation clear.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I have a simple access search form , that's based on a query that fill parameters from the form textboxes, when the access form loads its keeps prompting for parameters value which looks ugly .. I want to open the form, displaying all the records in the table and filter when i click search ..
I have a data entry entry form, that i want to generate success message after successful insert in database. I have done it in the button event if no error happens, still if i left all fields blank and clicked save, it displays the message ..
I need to change that to display please fill the textboxes then click save , and display success message when the row is actually inserted ..
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
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.