I want to create an attribute called "order_line_price", which is basically the quantity field * the cost per product.
I have written the following SQL query which works fine:
SELECT Order_line.order_number, Order_line.product_number, product_name, quantity, (quantity*price) AS [Order line price]
FROM (Order_line INNER JOIN Product ON Order_line.product_number=Product.product_number) INNER JOIN Price_band ON Product.price_band=Price_band.price_band;
I can create a table from this query, and all is ok. However, I want to store the value of each order_line_price next in its appropriate row in my Order_line table. I cant do this no matter what I try. I know that what im trying to do is store a derived coloumn, however I need to do it, because I have an attribute elsewhere which is the SUM(order_line_price), which I want to limit by specifying the order_number for which to add the order_line_prices up for.
So basically, how can I store a derived column like that? I guess I need to set something up in the default value property and lock the coloumn or something?
Ive posted here before, and havent had replys. So if your reading this and dont know the answer, but do know the link to a forum or chat room with speedier replies, please post the link.
At the moment i'm sotring the 'image_date' as an OLE object datatype. Is there anyway that i can get access to automatically populate the attributes 'resolution', 'created' and 'file_size'? or could this be done using a different datatype for the 'image_data' itself?
I was wondering if anyone might be able to help me here. I was trying to write up a technical report for the Access database i built. Are there an easy way of exporting all the tables with their attributes in Access?
For example, in the student table, ID FirstName LastName ...
I have a DB with about 50 tables. I have arranged them in a particular order in the relationship viewer and would like to print out as much of the viewer as I can by choosing the paper size and/or setting a scale factor. Access does not appear to let one do either. When looking at the relationship page, the 'page setup' under File ->Pagesetup is grayed out. Selecting 'print' causes the relationships to be printed in some sort of predefined manner, on 81/2x11 pages. Is there anyway to control how this view is printed?
On a related note: When in the relationship viewer, the only way to scroll the view is by the margin slider bars (the mouse wheel does not work). SHould the mouse wheel do the verticle scrolling? Also, if I want to move two or more tables (at the same time) in this view, how can I select them?
Code: Public Shared Sub Main() Dim path As String = "c: empMyTest.txt" ' Create the file if it exists. If File.Exists(path) = False Then File.Create(path)
I'm creating a database of companies. Every company has at least one field of services they provide. There are three main groups which contain all the services (Let's say I have three tables).
What I need is to have a form/table (query?) where I can assign to a company any number of services from any group. Is it possible to do it in a form where I could simply add a service by choosing a group first and then a proper service, and then add more in the same way?
Recently I have started working for one of the company where I have to deal with one of the access file. this file has lots of tables containing many fields.
My question is
How can I get all the tables name, their fields and attributes in Microsoft Word file. I have tried opening table > design view and copy text but it doesn't work. also tries coping table and paste in in word file but it takes ages
I have a table in msaccess which i would like to use as a search term to search values in another table. What i wanted to do is search the table with attributes and save all found attributes to a new table with its primary id.
Search_Keyword_Table Id ---- Search_keyword 1 ----- Size - S 2 ----- Size - M 3 ----- Size - L 4 ----- Size - XL
I'm wrestling with the issues; in other threads, it became apparent that because I could not know ahead of time what I will need to know about a given entity, I will use a table to enumerate attributes that is applicable for a given entity.
However, the stumper is that what if an attribute should conform to a set list of values? Since they are dynamic, I would have problem predicting what I will need to be able to lookup, and am even don't know whether I will need a one-many lookup or many-many lookup.
I thought that generic lookup table with a table listing "classes" of lookup would allow me to have one big generic lookup table while using "classes" to act like virtual tables so I can then set the query to appropriate "class" to return just right set of values.
But as I thought about it, I ran into some issues which is pulling me toward the crazy idea that I should have freestanding tables, and use a field in tblAttribute to give me the table's name so I'd know which free-standing table it points to, and have the necessary key to lookup the values within that table.
Even though my gut instincts tell me that I shouldn't be going against the conventions of database design (who the frick goes around creating free-standing lookups?!?), I'm simply not sure how I can use a generic lookup table to hold all information.
For example, suppose I was given a list of values that has its own categories. Since the former design allows only for two level (lookup and lookupclass), where am I to insert that extra level?
Furthermore, I found myself needing a set of virtual keys to reference a certain "class" of lookups for report purposes. That means I need an extra field in my lookup table than I originally anticipates. What if I find myself needing one more field that just won't fit the generic lookup table?
So does anyone have suggestions on how we would create a placeholder for a lookup table that will be made just in time?
I have a table that includes Employee's Names, Salaries, and Departments (I also have a Department table, listing each Department)
I need to have a query that will return a listing of each department, the highest salary within the department, and the number of employees working in the department.
The only thing I've been able to do so far is construct a query that prompts the user for the department number, then returns the max salary or the # of employees. I'd like to have all that data in one output when the query is run, without prompting the user to input any values.
I'm new to Access and I'm trying to create a table to store students' information. There is a "Birthday" field and an "Age" field in the table "Student". I want to derive the "Age" value from the "Birthday" value. So that each time I just need to input the value of "Birthday" and then the "Age" value can be generated automatically. However, I tried hard but couldn't find a solution. Can anybody help me with this problem?
#2Accounts Col1: Autonumber Col2: Drop down to select a concatenation of Lastname & FirstName. These fields are numbers from table #1 that display the corresponding names. Col3: ...
My query code below does work. However, it displays 1 - 1 - Account Name. I would like the actual "contact name" and actual "account type", not their corresponding unique numbers. Code:SELECT Accounts.[Account ID], Accounts.[Contact Name] & " - " & Accounts.[Account Type ID] & " - " & Accounts.[Account Name] AS [Account Details]FROM AccountsORDER BY Accounts.[Contact Name]; Any hints?
I am doing my comptuer science coursework and one thing I need to include is "how does access stored files" and the basic description of file organisation. After some googlging around though I have found nothing, can anyone hlep me out on this?
Hello, I am designing a query as i have been advised in the following Quote: Doc ManNow, you write a couple of queries. As a parameter to the queries, choose a date that will be your archiving cutoff or split point. Usually the last day of some month or quarter. Doesn't matter as long as you are consistent about it. The technical cutoff will be, in effect, 23:59:59 of the chosen date. The first record to be KEPT will be 00:00:00 of the next day in sequence.
Query #1 - Compute stock on hand as of your cutoff date. Create a single stock-on-hand transaction with the cutoff date. Put it in a temporary table until you need it. This will be a two-layer query. I.e. a query of a query.
Query #1A - a summation query grouped by item number for all transactions earlier than the archiving date so you can get the "inventory of X at archiving date"
Query #1B - an append query that draws from the summation query and feeds it to the temp table. The stock-on-hand record will have the archiving date
. I am able to get "inventory of X at archiving date" and append the results to a temporary table but I can't see how to append the "archiving Date" data itself to the same table as the "Archiving date" is entered via parameter prompt? Any ideas?
I know that you shouldn't store totals in Access, but I can't think of a way around what I want to achieve and wondered if anyone had any ideas.
An item on stock will move from one location to another, I will need to list the 'balances' of this stock at each location, easy enough to do, but there are hundreds of item movements per day and the users do not want a history of movements to be kept but do require an ongoing balance.
e.g. 100 of the item moves from A to B, this movement record gets deleted, how would I know that the item stock at A has been reduced by 100 and B raised by 100?
I have a database that stores customer records and their associated insurance details. I need to be able to track any changes made to that record within a set time period ie if details are changed fine it is reported next time report is run. But if details are changed more than once in between reports then first detail change is lost.
I would like to work out a way that changes can be written to a ??seperate version of the table?? and stored in there to be reported seperately and not just the final change as is the snapshot nature of a report? Is this possible? Could I possible make another version of the main table appended onto it? I feel I 'know' what I need to do but not how to even begin it! Any help would be appreciated.
I am currently designing a contacts database for my business and need some advice on how to store addresses.
As I see it, I can either use a single field and carriage returns, or multiple fields which for some records may leave some blank fields.
The data will be used to perform mailmerges and will also be output to a contacts directory and I would be looking to display the address both horizontally and vertically. Is there a simple way of manipulating a multi line field so that it can be displayed on a form across the page on one line in a report?
I've recently begun building a database to keep track of stock at work. Nothing particularly special or difficult. I have a little bit of prior experience with Access and VB, but not heaps.
Basically, I've created a tables for parts, companies etc, and am relating all the data together.
At the moment I've made a form that allows you to enter a new part, with Part Number, Description, Category, Supplier, etc.
The complication comes when I want to create an ASSEMBLY of parts. I'd like to create an assembly (which has a lot of similarities to a part, in that it has a part number, description etc), and that assembly needs to store a list of parts that it includes. A simple assembly might include a few items, ie, a bowl of meatballs includes the bowl, a fork, the spaghetti, and 5 meatballs. A more complex assembly (a complete dinner for 5) might include 5 bowls of meatballs (a sub assembly), pepper and salt, 5 glasses and two bottles of coke.
I'm not sure how to best store this assembly data...
I can't really have a table with a finite number of "part" spots because the assemblies get quite large. I'd rather not use an ugly VB macro that stores the PartID's with quantities either, as that could get thoroughly out of hand pretty quickly.
I'm sure there must be a simple method for doing this, but without having a clue as to what it might be called I can't really look for it in help!
I've created a simple database in which we enter order id (automatic), date (automatic), customer, po#, shipping date, and ship via.
then we scan the order (which may be from 2-20 pages long) into the computer so that we do not need to keep actual paper (trying to save on office space).
these files then get inserted the scanned object subform (containing the fields scan number, object, and order id).
I'm realizing that because we'll be scanning quite a few orders that this may take up quite a bit of space, i'm wondering if linking the objects rather than saving them within the database will help.
the only problem with this is that if we move the files containing the actual scanned images, that the whole system will get screwed up.
How do I create a table relationship where a secondary reltated table stores past dates, status code and customer ID. For example: I want to keep track of the past dates that an order was revised and why it was revised. So, if I have a customer who was due for installation on 10/21/04 and status is PEND for pending. THen on 10/18/94 I change the date of PEND to 10/25/04. I want to keep track of the times it changed and the reason why. HOw can I make the program automatically create a record in the revision table storing the past code, reason and date using customer ID as key and teh revision table would allow multiple records for each customer ID. DId I make sense?
I'm building a questionnaire/survey database for my work. Everything seems pretty straightforward, but I'm a little unsure about how to store the survey configurations.
I'm assuming that the survey will change sometime between now and the end of time so I'm tracking survey configurations (which questions and in what order). Right now my "Configuration" table has two fields: ConfigID (Autonumber), Questions (Memo). The 'Questions' field is a space seperated list of question IDs. The other way I could've done it is to use three fields: ConfigID (Long), OrderNum (Int), QuestionID (Long).
I figure the first way is more memory efficient in the long run and it will take much less time to add a new configuration.
The way I'm doing things now works for me, but I'd like to know if anyone thinks I'm setting myself up for trouble down the road or if my way is actually less memory efficient (I'm not as concerned with processing time).
I have a choice of either calculating a field or storing it.
Specifically, I have two pieces of data ... departure time and arrival time which I have taken from another source. This other source also has the difference between these times. Currently, I am not storing the difference in a field as I have opted to calculate it in my database.
However, I am thinking that maybe it would be better to store it vs. calculating it because I have 35, 000 records and storage space is not going to be an issue.
What do you suggest if I my main concern is speed and effeciency?
