How do I make my database so only the creator (myself) can edit the tables, forms etc and other users see an interface starting with the switchboard, which they can't use any database tools except what the forms allow them to do?
I have recently inheritied a database and find that there are functional differences between different versions of the database. The database contains over 30 very large tables and I am unable to find the differences between the versions. I need a process or tool that I can use to compare the different versions to find the table/record/field differences. I am up against a deadline and am needing a solution ASAP.
I am working on a section of code that when a user clicks a button it looks at a table called TBLVersion and increments the version number. The version number format is 1.0.1 what I need the code to do is increment the last digit by one for example to "1.0.2". I got the flowing code to work in excel but could not figure out how to translate it to access.
I have been trying to come up with a solution for a problem I am having for a while to no avail. We have a backend database that stores various tables full of data. We then have a custom Excel Ribbon that connects to the database and pulls in the different tables depending on the user selection form the ribbon. Everything is working well on that end. The problem I am running into though is that in the development phase of the ribbon and database we had multiple versions and so there are still some people who are using old versions of the ribbon and therefore not connecting properly to the database. Is there some type of code I can add into the database and ribbon where it checks for a specific version to ensure the user is using the most recent version?
Basically, before any type of query is run to connect to the database the ribbon would have some sort of label on it somewhere and the database would check for that label and if it is correct, the code proceeds and if not a message box appears that tells the user they are not using the most current version of the ribbon and exits the sub?
I am trying to open a MS Access Database which was made in MS Access 1997 or MS Access 2000, at the moment i am using MS Access 2010, i cannot open the database or link the tables.i do not have MS Access 2000 anymore.
Ive just started creating the table..and Ive put fields like name/address etc as text but there are a few fields that need you to select an option...so i want to use the "lookup wizard" to create a listbox or combo box dont know which is best.. BUT the problem is when I select lookup wizard it says "unable to start lookup wizard. The lookup wizard doesnt apply to fields of this data type".
I need help making a front and back end to my database. How should I do it!?!? All I know is what I should put in the front end and what goes in the back end. The rest needs to be explained to me somehow...
I have discovered a problem with my database and wonder if anyone here can point me to the best solution...
The problem is this... when I took our company database over about 3 years ago it was around 45MB... now it is almost 350MB and growing steadily.
I have today discovered the main cause of this... the audit trails on a couple of the tables. If I remove these 2 fields only from the database it cuts it down to under 100MB. The Audit trail is quite important for us and so I'd like to keep it if I can. It is stored in a memo data type (the data is well over the 255 char limit of a text box). Is there any other better way to store this data or is there anything I can do to reduce the size of the memo data type?
If you make your database into a executable file to package it, does the other person you are sending it to have to have or own Access to use it. I was under the impression that I could create a database, package it as its own program and give it to someone that does not have access and it would still work? If not, how would I do such a thing.
We have a shared personnel access database for our department. Another department is wanting to use the same database. Is there a way to go about deleting all the info and making a template to give the other dept to use?
As my database is growing and hold more and more data i want to make a daily backup to the local hard disk (it works on a network now) automatically.The way i want it to work is as follows :
When a user quits the application i want to check if there is a copy already existing with the date of today.
If it does it skips the copy process and just quits.
If it doesn't, i want it to make a backup in a directory. if the directory doesn't exist it must be made.
The backup file name must hold the date of today off course.
I realize that i have to have a procedure to delete obsolete (outdated) backups as well, but ill worry about that later.
Off course Ive tried this a few times, otherwise i wouldnt ask it here. But i seem to fail every time..
there is a need to make access database (access 2007) accessible over net. I know Access Database is not web based application. So I want to know if there is any way of making it accessible via net.
I need to start using the database I've created (desktop database). However, I don't want my current version to be the final version.
Should I create another file to work in and use the old version for data entry? When I am ready to start using my new version, is it easy enough to transfer all the data from the old?
I have created a database of club members in Access 2010. Each day I need to generate a report of who comes to the club. Up to this point I have been using an Excel spread sheet of members that I copy and paste to new daily spreadsheets each day. how to do this.
I've created and tested my database. What step or steps do I take now to make it so it's a program that only shows the forms and menu's I created, not all the Tables, Queries etc and the formatting options? Is there a link that explains what to do step by step?
I am working on a database used in recording device characteristics/test information. The main table of information has dozens of columns for test/part detailed information. When inputing the data for each specific test, many of the info. details are repeated when testing say 20 devices of the same part all at once. Rather than retype every piece of detailed information in every field, everytime, is there an easier way? Does anyone know of a way to make specific fields copy/paste the previous record's information in the fields automatically when a new record is created? Please, if anyone could help or has ANY ideas, let me know...
Are there any issues with converting an older 97 database to 2003? Is it a straight conversion, or will there be differences that affect the way the database will run if converted? I've read somewhere that it is possible to use the newer version to open the database w/o converting it. It seems silly to have to install 97 on a new computer in order to view the db.
I just created a calendar pop-up for data entry in Access Version 2002 and it does not work with Access 2003. Any help from anybody would be appreciated!
An application that I made was created in Access 2000 as I was told that all users had at least this or newer. Of course a user with 97 popped up. Instead of having them purchase 2000 or newer I converted my app to 97 version. I expected troubles with references. So far this has only been a phone conversation and I plan on going there later today. The user says hitting alt/F11 does nothing... no code window comes up. I had her look through the menus for the code window but she says there is nothing there. She is getting runtime 3433 (she thinks) and unrecognized database format when trying to open a form. The database did open when holding the shift key though.
Before I go there, how do I open the code window for 97? Any other suggestions? I bet this is a reference thing but there may be a problem with their access install too. There are 2 users at this location with the same issues... at least it sounds like it.
I have a database which is use at busy times to run the delivery side of our Floristry business. The orders are entered,assigned to a delivery area, address labels printed. When it comes to delivery day orders are selected from the list ticked off then printed a make a list for the driver.
It was built using Access 97 when it first came out. Since then the software was upgraded to Access 2000 many mods have been made each year to improve the performance and the number of things it can do. It now has about 15 tables and a lot of queries. Not being an expert with Access a lot of the design has been on a trial and error basis. Put it another way the main form has many hidden fields to make things work behind the scenes. But it does most of what I want it to. I have now go to the point where the main query is saying that I can't add any more features because I have to many fields in it.
So the time has come to look at re building it for a number of reasons.
1. It is a stand alone database on one Pc.......... I would like to have it on a network to 3 or 4 Pc's around the shop. 2. Some of it needs to be redesigned to take out my ( it might not be the way a designer would it but it does work) type bits. 3 I would like to be able to use the system for all orders received on a day to day basis. So it will need to be used by other people.
My question today is Should I be looking to rebuilt it using Access 2003 + the extra software so that i can run it on more than one PC.
Or would it be better to wait few months till Acess 2007 comes out and start from scratch.