Ok, I am getting to know MS Access much better than now that I am asked to design a MS Access database...
We have a small company of 20 users. The reason for the database creation is to keep track of the hardware & software inventory that we have. Sometimes, users borrow softwares or laptops and we want to keep track of it. My boss also wants to know how many workstations and how much memory we have in there kind of things. You know, basic inventory...
So, we have 3 servers, 20 workstations, 5 printers, licensed softwares, few hubs, and router... Nothing fancy, a small shop.
So to design this database, I read some MS Access database design guidelines... However, I am still not clear whether I have set it up right because I learned that design part is the toughest part. If the design is good, then rest should be easy... At least right?
So I am thinking about creating 2 tables. Why? Our inventory really is hardware and software, I think. I don't think we have other things...
One table I am thinking of creating is Hardware_Inventory and the other Software_Inventory since that is our goal to create an inventory to keep track of what we have, who has it, where is it, when did we purchase it, how much is it, and what is in the hardwares?
So I created in each table - fields, but I'm not sure whether this is done correctly. Again, I wanted to answer few things if someone were to look at the database: what is it, where is it, who has it, when did we purchase it, how much is it for soft and hardwares, and what is in the hardwares?
Note: Property_Code is going to be a key number or a property tag I will get to put on it and have it as a Primary Key.
Hardware_Inventory_Table:
Property_Code
Description
Make
Model
Model_Number
Year
Serial_Number
Purchase_Date
Purchase_Price
Warranty
Department
Location
On_Loan_To
Duration
Checkout_Date
Checkin_Date
Comment
Software_Inventory_Table:
Property_Code
Description
Vendor
Version
Product_Key
Year
Purchase_Date
Purchase_Price
Warrnaty
Department
Location
On_Loan_To
Duration
Checkout_Date
Checkin_Date
Comment
Then I was going to link the Year, Purchase_Date, Purchase_Price, Warranty, Department, Location, On_Loan_To, Duration, Checkout_Date, Checkin_Date, and Comment....
I need some expert advice whether I have it set up right in the design, whether I have chosen the correct fields, and whether I have made the correct link? Or anything that I need to address or re-design...
Hi all. I'm trying to figure out how to make a SQL query require ALL of the data in one record match ALL of the data in another record. I may be using the wrong term when I say record.
What I have is a job order form where I list order details. I list location, start date, client all of the skills the job requires. I also have a candidate form that lists candidate locations all the skills they possess. The skills for each form are drawn from a SkillsInventory table. Once I enter all of the job info into the job order form, a subform lists all matching candidates based on state, availability/start dates, skills and a couple of other items. Everything works fine with the exception that I am returning any candidates with any of the skills in the job order verses only those candidates with ALL of the skills I select for the job order.
I would assume I would enter something under one of the columns in my sql builder/design mode. If I view SQL view, here is what the statement says:
SELECT [EmployeeSkills].[SkillID], [JobOrderSkillsList].[SkillID], [Employees].[LastName], [Employees].[FirstName], [Employees].[MiddleInitial], [Employees].[EndDate], [JobOrders].[OrderID], [Employees].[City], [Employees].[DoNotCall] FROM ((JobOrders INNER JOIN Employees ON [JobOrders].[StateID]=[Employees].[StateID]) INNER JOIN JobOrderSkillsList ON [JobOrders].[OrderID]=[JobOrderSkillsList].[OrderID]) INNER JOIN EmployeeSkills ON ([JobOrderSkillsList].[SkillID]=[EmployeeSkills].[SkillID]) AND ([Employees].[ContactID]=[EmployeeSkills].[ContactID]) WHERE ((([Employees].[EndDate])<=Date()+14) And (([Employees].[DoNotCall])=False)) ORDER BY [Employees].[EndDate];
I have a database that currently has security in place so that users input their own usernames and passwords to access the database. The users have recently been added to a windows 2000 server and I want to be able to use their windows 2000 server logon credentials to provide them with automatic access to the database. Is there anyone out there who knows how to set this up? It is a rather urgent request if you could get back to me either on this forum or via email
I am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
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.
Since I left school I have had to jump into application design on my own because I am finding it difficult to find work without 1 to 3 years of experience typically required by the current job market. This leaves me without any gut feeling for how to charge my customers. Charging by the hour is difficult to do fairly because I am not as efficient as more experienced programmers. Charging by the form, query, report, macro, or module, however, doesn't accurately capture the time variable associated with extensive scripting. Any guidelines offered in regards to charging and possibly ballpark rates would be hugely appreciated!!!
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 am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
We have two computers in a work group. On computer1 I have the back-end and front-end database files in the shared folder and 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the error message "Microsoft Access can't Find The Database 'C:Documents and SettingsAll UsersDocumentsdb.mdb' Make sure you entered the correct path and filename" On computer2 I have the front-end database files in the shared folder and pointing to the same back-end database on computer1. Again 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the same error described above.
I expect that this is some sort of windows permissions issue? There are some clues to this fact .. The two users that can't access the database are limited accounts, but I tried making them administrators and this had no affect. Their shared documents folder does not have a hand underneath it?
Any help on this appreciated as it's really starting to annoy me now!
A few years ago I’ve made an access database on access 2000. The problem is that now I’ve installed the office 2003, and I can’t make the database work properly.
At first says that are missing those files: “tshoot.ocx”, “msioff9.ocx” and “msowc.dll”; so, I’ve copy them from another computer using office 2000 and now only complains about “msioff9.ocx” saying that my database contains a reference incomplete to it.
Is there no other way to convert my database do work properly with access 2003? What can I do?
The company I am consulting with uses Access 2000 and has no intentions of upgrading. I currently do not own Access on my laptop.
I was planning to purchase Access 2003 for my laptop but am concerned that files I create in 2003 might not be "editable" in 2000 even if I choose the 2000 format when creating new databases.
I'm just wondering if anyone has tried creating a file in 2003 (using the 2000 format - as I'm told you can choose what format you want to use) and then edited it in 2000. I want my client to be able to edit the files in 2000 once I've moved on. (I can get 2003 for about the same price as 2000 - so my preference would be to get 2003.) The other obvious reason for going for 2003 is that I could run into the reverse challenge if I own 2000 and my next client uses 2003. At that point, I'd be forced to upgrade to 2003.
My databases are not complex - but do include some customized macros.
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
I have one Project in Ms access 2000. If I create Setup(Package) it's working fine in Access2000 but for Access 2003 I need to install Ms Access 2000 Runtime. Kindly tell me how to install Access 2000 Package in Access 2003 without installing Access 2000 Runtime. Can it support backword compatibility ?
I have created a database in Access 2007 that now works well, and one that I'm quite proud off. However, I can easily convert it to an Access 2000 format as can anyone else here, but when I load it up there is a major problem.
I have used the tab control in my main form and that has three tabs on it. However, it's positioned correctly in Access 2007 it's not positioned correctly in Access 2000 as I have to move the tab control down a bit, but that would seem fine. So I lowered the tab control form and changed my form layout slightly, but even then the tab control over all over the Access 2000 form whenever I interact with the tabs - most bizzare.
I am doing some computer work for a company that has an Access 2000 application. This app is split up between a program database that contains the forms, reports, etc. and a data database. Both the program database and the data database are located on a Windows 2003 teminal server. There are usually two or three remote users logged into the terminal server, but this number is about to increase to 6 or 7. I am concerned that these user's will all be running the same copy of the program database. I have read that this can lead to performance problems.
I was wondering if anyone hear thought either of the following would be an improvement:
1. Put a separate copy of the program database in each user's profile on the terminal server.
2. Rather than keeping the program database on the terminal server, put a copy of it on each of the remote client pc's. Then set up a VPN connection to the server and use this to link to the data database.
If anyone could tell me if either of these options would lead to improved performance, I would really appreciate it.
At the moment the company Im with uses Access 2000, however ive been told by a few people that Access 2000 had alot of issues and it would be worth informing the company to upgrade to 2003 asap. Is there any major concerns with 2000? Some of the databases currently being used are very large and complex. Any chance data could be lost/displayed incorrectly? etc
I'm new to MS Access. I want to know about compressed/reindexed databases.
What happens when a database is compressed? What happens when a database is reindexed? Why is it important to periodically compress and reindex a database?
I have records in the database that I need to pull up by local time zones, what would be the most effective way to do this?
