I was hoping you guys would have a recommendation. Do you know of a book or web site that offers workbook examples to help practice learning how to understand existing databases?
My biggest problem with databases has never been designing them but learning how to follow someone else's work. Some place to practice on this deficiency of mine would be great. Any thoughts?
I have tried to figure out what the difference in functionality would be between 1 and 2. In the latter I have just created a series of relations between the last two tables (but that structure could be used throughout the whole DB instead of hanging it together with one relation between tables as is the case for the rest of the DB in this picture).
So there can be three different situations with this table structure: - linking all tables together via multiple relations - linking all tables together via a single relation - a combination of both, such as in the images.
Why would someone choose one versus the other? "Which is better in what situation?"
I've been fiddling about for a while now, but in a structure such as this it doesn't seem to make a difference. Or maybe there are differences in use/design, but on a level that I have not explored yet.
Could anyone explain this to me a bit? I have multiple books, all of which handle basic relations but I have not yet seen an explanation for this question. I think understanding the whole relationship topic is critical to be able to see other pieces of the puzzle fall into place later on. And as of yet, this is really fuzzy to me.
Omits records that contain duplicate data in the selected fields. To be included in the results of the query, the values for each field listed in the SELECT statement must be unique. For example, several employees listed in an Employees table may have the same last name. If two records contain Smith in the LastName field, the following SQL statement returns only one record that contains Smith: SELECT DISTINCT LastName FROM Employees;
If you omit DISTINCT, this query returns both Smith records.
If the SELECT clause contains more than one field, the combination of values from all fields must be unique for a given record to be included in the results.
The output of a query that uses DISTINCT is not updatable and does not reflect subsequent changes made by other users.
So, from what I understand of this, if any of the fields in the record (or row, whatever) repeat then it is not displayed. Correct me if I am wrong.
The problem is that when I try and use it in my DB it return all the fields regardless of the Distict clause, unless I am only querying one field, which is next to useless.
For example when I make a test table that has repeating words in one field, with a unique ID for each one, the distinct clause works when I display the words field alone and not when I display the ID field as well.
Can anyone explain what is happening or what I am doing wrong?
I have to create reports from an Access database used in a commercial application. The backend uses Access but the front end does not.
The vendor does not document the data or provide any support for that. The database has over one hundred tables and thousands of fields.
I'm thinking I'll create small transactions in the application and then study the database to see what has changed. But this seems overwhelming considering how many tables and fields there are. So I'm looking for advice on how to approach this.
Hello i am a college student and i was just getting on with my database assignment. i don't want any one to do it for me i just want someone to point me in the right direction. i am making a basic Encyclopedia on planets for my project. i have made one form which i want all my other forms to look like. this form is getting its information out of queries. this form is opened when i click a picture of the planet. so i was wondering if it was possible if i could link all the picture up to the one form but each picture opens a different set of data with in this form. i have already thought of just copying the forms and changing the control source. just wondering if there is a different way of doing it.
ok, let me please ask this question regarding a payment relationship in my database
it will be paid in four ways, cash, creditcard, cheque, paypal
each of these payment types will have their own features..
eg creditcard (name on card, card number)
cheque (cheque date, date cleared)
paypal (username...YOU GET THE PICTURE
so is this below way a good way to store these details, or can i do it with 4 less tables..
http://bb.1asphost.com/antonyx6/untitled2.jpg
if this way is correct, i dont see how each id will be entered.. eg if i enter some cheque details.. will that lead the chequeid to be linked to the paymentid, and the paymentid to the bookingid, and the bookingid to the booking details etc
-Existing Access Database contains tables with 1-2 million records
I would like to add a field[dol] to an existing table[rei]. I need this new field[rei].[dol] to be populated with existing data from another table[main] based on the associated field[main].[account1] or [main].[account2] or [main].[account3].
In the [main] table. There is always data in [dol]. But there is NOT always data in the [account] fields. Sometimes there is multiple account numbers per [dol] but not always.
Customers will ALWAYS have at least 1 [account] number and [dol]. Some will have multiple [account] numbers and [dol]. Sometimes these [account] numbers are the same in multiple fields[account1] [account2] [account3].I just need to do a lookup or something to find the [account#] and pull in its [dol] from the [main] table and populate it in [rei].[dol].
I'm creating a database that keeps track of printing jobs at a printing company... I started my project by drawing out how I want the databases to be configured.
I was going through a book that was made for access 2000, but I need to create this in access 97 because that's what the company has on their computers. One of the features in Access 2000 thats not in 97 is subdatasheets...
Basically, what I want to do is for each printing job, there can be a bunch of different tasks that need to be completed and billed for. For example, on one printing job, they need to design a logo, and then they need to print it out and send samples across the globe, and then they need to create a pdf, etc. This is going to be different for each job.
What I figured I would do is create a separate table to take care of all of the different tasks that are related to each job. This table would have the primary key of the job from the main table for each individual job, and then they would be related in a one (MAIN entry) to many (tasks) relationship.
Is this correct in how I want to do that? How will I do this inside a form, I want them to enter the information in table that expands as they put more tasks in?
This might be a very simple question, I just want to know if I'm going in the right direction.
I have been reading a lot about splitting databases on this forum. I still have some questions. 1) Will the FE (Front End) still show the tables? 2) Will users still be able to edit the forms, reports, etc.? 3) Will my code be hidden 4) Will all the users have up to date data showing when they open the Database? 5) Can more than one person open and input data in the database at the same time?
I also want to make an MDE copy, do I split first or make the MDE and then split?
The whole point is the following: I want the people (maximum 10) that will be using this database to only be able to do enter and view data. They should be able to generate the reports but not create new reports. I only want ONE person to be able to edit the forms, code, and reports. How would I do this.
Forgive me if this is in the wrong forum, so MODS, do what you will.
I'll come out and admit it right now, I'm a newbie here and have just started using Access2003. I'm in a city government so I need other users to be able to view and access my database, BUT I don't want them to be able to edit or change things. I want to be the Owner/Administrator of the database and no one else. I want to be the only person that can make changes.
Is this possible in Access 2003? Can other users only open it in Read-Only format but when I open it, it's editable?
I am new to Acess, I am trying to merge 2 Access DBs and am not sure of the steps to accomplish this, if it can be accomplished and/or are there any tools to reach the same goal.
I have an MS Access database on a server which acts as a back end, with about 30 users using the data. They each have a copy of the MS Access front end located on their PC's.
Every time I make a change to the front end, I have to redistribute the new version to each PC.
What I am wanting to do is put a single copy of the front end on the server, and adding a shortcut to this front end on everyone's PC's. This would allow me to make changes to the front end without having to redistribute to all users.
What I was wondering is, if I put a single copy of the Front end on the server and simply shortcut to that front end, will it cause any problems, or are there any issues that I should look out for?
I have a Form that refers to two Reports, both of which refer to two query's one for each. the whole lot(1 Form, 2 Reports, 2 Querys) is in one mdb file and the actual database is another mdb file. How do I get my objects to get their data from the main Data Base File? the 5 objects are acting as a small report making application.
:confused: Does anyone know if there is any way to link to seperate databases so that any information entered in one will update the same information in the other and visevirsa?
My company has a database. I downloaded a copy of it to my desktop to work on it. Can I integrate my changes to the original? (copy/paste,export etc) I hope so.
I have three different databases, engineering, properties, and my contacts. I would like to have one switchboard that I can put on my desktop to access all three databases. Is this possible?
This post is really aimed at someone that has experience of network databases and the problems they can pose but if you can help at all that would be great!
I work for an insurance company and we have created a database for registering complaints on. The one we currently use is a single .mdb file which can be shared by up to 60 people at any one time. This is creating a lot of problems when the queries and some VBA code are run. I therefore made a server file which is just an mdb file with data tables in and NO forms or queries. This file is stored on a shared drive on the network server. We then created a client file which contains all of the forms and queries and code. This file contains linked tables to the server so when data is entered into the form, it "Sends" it to the server mdb file. The client is installed on each of the local machines c:. The problem with this was that if we made a change to the database, we would need to reinstall the client on every single user pc. This would of took ages. I therefore made an auto-update function that checked the version number on the server and if the server number was greater than the client number, a simple .bat fiile was run which copied the updated client file from the network to the relevant users local disk. The problem we have now is that our IT department are concered that if we make a change to the client and all the staff log in at 9am for example, it will start doing multiple copying of a file around 8mb in size to around 60 machines. They are only running on a 2meg pipe so this could cause some problems. We are not looking to change the client & server idea but does anyone know if this will have a big impact and infact if the updates for 60 machine is the equivalent or lesser of 60 people sharing the single file i mentioned earlier. If the IT dept are happy with 60 users accessing the same file at the same time, which they currently are, why are they unhappy with it updating these machine using the new method.
Would really apopreciate any thoughts anyone has..
I have a database with two tables, Buyer and Products, with one-to-many relationship. The key of Buyer is an autonumber ID, which is the foreign key to table Products.
The problem is that i have two copies of this database with different records (with ID starting from 1 to each one) and i want to merge the databases into one.
Any ideas how to do this without lose the connection of the records?
How do I merge these two datbases? I have downloaded them from Microsoft online templates, here http://office.microsoft.com/en-gb/templates/TC010178391033.aspx?CategoryID=CT101426031033&av=ZAC000 and here http://office.microsoft.com/en-gb/templates/TC010185481033.aspx?CategoryID=CT101426031033&av=ZAC000 and I want to have the two databases as one so that there will be a fourth tab on the cintact management database with the order form on? I want to be able to link the two so I can have all the customers details and orders together and print off reports. I really have not dealt with Access before so I really dont have a clue. Any help would be truly appreciated. I am sure it is easy but I just cant work out how to do it.
We are using an Access database for off-site data entry. We therefore have one master database we keep in the office and then a "template" version -which is identical to the master version except no records - we bring to each site, do the data entry and then merge that data back into the Master database.
Can anyone help suggest ways to make the data merging process more efficient. The database has approx 12 tables, so I dont' want to create an append query for each one every time. Is there a way to just "merge" two identical databases??
hi all! i have recently been set a sort of project to do and i have to create a database that is for booking customers into a hair dressing salon, this is not for a real company, it is made up but i have to do it and i don't have a clue how :( i need a customer form with all their data on, this can be random a booking form that i can book the customers into different treatments and this is the hard part i need a staff form and some how i need to know what days they work on so that it will come up on the booking form so that you can search for available days, its really hard and im really stuck, can anyone Please help :confused: hope i hav'nt confused anyone
Hi all: Would appreciate any help that anyone can offer. Have a client with an Access2K database that gives the dreaded "...No read permissions on table MSysObjects..." error. I'm trying to just get the data into a new clean mdb but Access blocks me at every turn.
Have tried compact & Repair Have tried JetComp Have tried TransferDatabase via code No luck, can't get at the data.
Now here's the kicker, the database is the back end to a VB6 application. The application continues to run fine and is happily accessing and updating the database. Any suggestions about alternate ways to get the data into a new clean mdb would be much appreciated.
I have 2 different databases. One for Archives and one for active claims. Both databases have identical tables. I'd like to create a query that will pull information from both databases. I'm pretty sure that I can do this with a union query, but I'm a complete noob with sql.
Can someone give me an example of the sql code to use to pull information from tables on both databases?
Is it possible to create a query that looks over two different databases for information. i.e I have two departments at work that have seperate databases and I need to be able to search for data in both of them on the same query.