I'm trying to create my own events (issues, action items et al) log database for project management.
I have attempted to have the events interrelate to each other. I am inviting comments, suggestions and the like.
Thank you in advance.
I am working on a database to keep track of meter readings from several meters. Am at the table design stage and have come up with two seperate table designs but am wondering what would be best.
Each individual 'Meter' tracks more than one 'Fuel'. All of the regular meter readings should occur on the last day of the the month. The difference between the current month's reading and the reading from the previous month is the usage for the current month.
Though rare, there are occasions when there could be adjustments to the meter. A meter may be reset to 0 or to any other number due to a number of issues (replacement, maintenance).
The usage for a Meter-Fuel combination calculated by the current meter reading & previuos meter reading is assigned to current readings' date, As readings should onlt be taken at the end of the month, all other readings should be adjustments ONLY!
Here is my one version;
tblMeter
MeterID (PK)
strMeterDesc
tblFuel
FuelID(PK)
strFuelDesc
tblMeterReadings
MeterReadingID (PK)
dtMeterReading
MeterID (FK)
FuelID (FK)
dblMeterReading
tblMeterReadings
MeterReadingID (PK)
dtMeterReading
MeterID (FK)
FuelID (FK)
dblMeterReading
tblMeterAdjustments
MeterAdjustmentID (PK)
dtMeterAdjustment
MeterID (FK)
FuelID (FK)
dblMeterReadingOLD
dblMeterReadingNEW
My other idea was to incorporate meter adjustments into tblMeterReadings and not have a sepereate table for meter adjustments
tblMeterReadings
MeterReadingID (PK)
dtMeterReading
MeterID (FK)
FuelID (FK)
dblMeterReading
blnAdjustment
The I would create a multi-field index of dbMeterReading, MeterID, FuelID, blnAdjustment.
So data with an adjustment may look like this
dtMeterReading, MeterID, FuelID, dblMeterReading, blnAdjustment
01/31/2005, 1, 1, 900, False
02/15/2005, 1, 1, 1000, False
02/15/2005, 1, 1, 0, True
02/31/2005, 1, 1, 100 , False
I think that the second version is the way to go, since I would still have to create a query to join data from both the reading and adjustment tables in the first design that would look like the data above.
Here what I consider to be the drawbacks to either table structure
Version 1
The first version requires more complicated queries to calculate the difference between meter readings.
Version 2
The second version will require some coding/querying to make sure that there are always two adjustment records for one date and determining which is the pre-adjustment and post-adjustment meter reading since it may not be true that the meter is reset to zero; it may even be set at number higher than the pre-adjectment reading.
Any thoughts on which design is better? Or any problems I could run into later with designing forms/queries/reports that perhaps I have not thought through?
THANKS!
Could someone offer suggestions on how to improve the database or the general structure of it?
All suggestions are welcome!
(Its an online retail project selling DVD's, CD's & Games)
hi. I am trying to write a code to sum the total cost of all jobs that are selected as 'yes' in a combo box.
Once the user selects 'yes' in a combo box, they enter in a cost for that specific job. Each client may have 10s of jobs. I need to write a code that will sum up all the 'yes' selected jobs for a client. I know it should be an 'if' statement but I can't seem to get it to work. I need this value for a report. How would I do this and where would i put the code.
Help is appreciated.
Here is the code that I was thinking of, I don't think its right but it might be a start.
Dim Count As Variant
Dim CountImplementedTotal As Variant
CountCost = 0
CountImplementedTotal = 0
Dim rst As DAO.Recordset
Set rst = CurrentDb.OpenRecordSet("ECM Details")
Do While Not rst.EOF
If rst![AUDIT ID] = Forms![audit info]![AUDIT ID] Then
If rst![Has Measure been Selected] = "YES" Then
Count = Count + rst![Total Measure Cost]
End If
End If
rst.MoveNext
Loop
Text47.Text = Count
Hi,
I'm doing a database for a CD, DVD, Game website could you take a second to review it and give me suggestions to improve things.
I've included my old and revised database to see what if done
Hi
I have a database for maintaining procurement contracts which includes a start date for each contract and a frequency of reviews required (monthly, qrtly, bi-annual, yearly). I need to be able to generate a report that will tell me when the next review is due for each contract, taking today's date into consideration.
This is the setup so far:
tblRegistry - contains field 'Commence' for the start date of the contract and 'Review Req' to indicate how often a review is required (monthly, yearly etc).
tblReviewReq - contains field 'Review Frequency' (monthly, yearly etc) and 'Days' to assign the number of days eg monthly = 30, yearly = 365 etc.
Next I have a query that includes the above tables using the fields 'Commence' and 'Days' and have created a calculated field to give me the next review date ie contract start is 1/08/07, review freq is monthly (=30 days), therefore the next review is 1/09/07. "NextReview:[Commence]+[Days]"
But how do I get it to tell me the next review date after the 1/09/07? Ultimately I'd like to be able to pull a report at any stage which will tell me all the reviews that are coming up.
Thanks
Hello,
This is my first post.
I have built an access database (Access 2002) which contains around 370 records.
It would be useful to be able to click a button on a form to review which records (forms) have been amended or what records are new.
This could be presented by either (1) sorting the records so the newest/or latest changed records came first, followed by the next most recent etc etc, or by (2) presenting a list of record names which could be followed manually.
I have tried several text books but have been unable to find a solution so any help from the experts would be very welcome.
Thank you ~ David.
Hello everyone,
Using Acess 2007
This is what I have:
I have one Query with the following:
Main.ID, Main.First Name, Main.Last Name, Main.Assigned Date
I created a Daily Report using this Query to tell me when I need to meet again with these people.
I have a Report that has the following:
Main.ID, Main.First Name, Main. Last Name, Main.Assigned Date, [Assigned Date]+30,[Assigned Date]+60,[Assigned Date]+90,[Assigned Date]+120,[Assigned Date]+150,[Assigned Date]+180
What I would like to do:
The current report shows ALL records with the requested information. How can I have the Query or Report filter out the records that do not have any of the review dates falling on today's date?
I hope I explained myself. If further explanation is necessary let me know.
Any help is greatly appreciated.
René
This database is for a car event that's held once a year. It has been a work in progress for about 15 weeks now and is basically finished. There is only a couple of errors and not sure where to start. The database is so big it is getting a little out of reach for me to organize everything.
Idea of the database is that I can enter entrant's information, there car details and any merchandise they want.
Main errors I’ve noticed are;
In email form if you select one user it still emails everyone.
In the car details form the induction box does not show the value list I created in the car table.
when entering a t-shirt in the products form you select the shirt size. Is this the best way to lay this out.
In the Order Form what is the best way to add a freight box between Sub-Total & Total where you can type the freight in and it's automatically added to the Total Box
Have a look over the db and let me know what ya's think.
Thanks
Dean
I have a form with date fields I need to calculate review dates for employees. Example 45 day 60 day 90 day what would be the best option to do this?
View 1 Replies View RelatedIs there a way to review / edit the actual SharePoint workflows in SharePoint created by Access Services after a web database has been published?
View 2 Replies View RelatedI'm having some problems with VBA code I'm writing that references a subform. I'm pretty new to VBA and am not sure what the problem could be. The parent form (TrackingForm) tracks dates different tasks were completed. The subform (Child2) tracks exceptions that also need to be marked completed. I need ALL dates to be marked as completed before the entire tracking record can be marked as completed.
I have the following code entered into the OnFocus event of the tracking records Me.Completed_Date field:
Private Sub Completed_Date_GotFocus()
If IsNull(Closing_Date) Or IsNull(Package_Received) _
Or IsNull(Upload_By) Or IsNull(Initial_Review_Date) _
Or IsNull(Me.Child2.Form![Date Exception Completed]) Then
Me.Completed_Date.Locked = True
MsgBox "Completed Date cannot be entered - outstanding items.", vbOKOnly, "Warning!"
Else: Me.Completed_Date.Locked = False
End If
End Sub
What ends up happening is that, if there is more than one exception record on Child2, the code only seems to care if one of the records (usually the first record) has something entered in the [Date Exception Completed] field. I can't seem to make it look at any successive records in Child2 to ensure they are also completed prior to unlocking the Me.Date_Completed field. I have googled this extensively over the last day and the only response that seems to recur involves using a Recordset function that I have never used and am unsure how to.
I've got a database that allows all users to review an address register. If they find errors or mostly get updated information they have another form they can fill out to make the recommended changes. Only I have access to the main DB to make the change permanent.
The question I have is there a way for Access to send me a notification that someone has requested the change?
I know that sending an email is doable - in Access. However, that's not an option for our network here. I was thinking something along the command prompt "Net Send" command. However I've not been able to get that to work by itself - let alone within Access...
I have used VB code in the past to store what PC is using the database, I could modify that to alert me whenever I open the DB up from my PC. But I was trying to get away from having to open this particular DB up every day and check for changes.
I am designing a database for my organisation. I have done most of it but am stuck on this. Ideally I would like to have a check box (in a table) that when checked a load of data is carried across from that record to a record in another table.
Given that I can't and don;t want to use VB is there anyway that this can be done easily?
I am having problems coming up with a Table design and need help.
I am trying to design a table that will have 8 categories, 47 subcategories, and then choices within those categories.
Much like the following (this is only one category example, there will be many):
(Main category) Floors -> (Sub categories) Joist, Carpet, Vinyl Flooring, Wood Laminate -> (Choices for Joist Sub Category) Structure Wood 2X8 Joist, Plywood 2X8 Joist, Structure Wood 2X10 Joist, Plywood 2X10 Joist
This only shows the flow if the main category is "Floors", sub category "Joist", and then the choices under subcategory "Joist". There will be others for the other categories, subcategories, and choices.
Can someone help me or steer me in the right direction in setting up the database table/tables to accomplish this. Oh and BTW, there will be prices attached to each "Choice" under the subcategories.
I hope that this makes sense... any help would be much appreciated.
I have 5 tables with the same data (row and columns). How do I make it into a relational table?
View 3 Replies View Relatedif i had a table with products and i want to keep a record of what has been chaged or added to this product, whilst keeping the old records how could i set it up in a databse?
the excel spread sheet looks like this
product commments
1 chnged this and that 20/08
1 modifyed component 21/08
2 newest model 3/08
Hi all, i wonder if anyone can help?
It's a simple question really. I'm currently learning databases and am doing a project, just to show that i understand everthing i've learnt so far. I have to produce a small database.
There's nothing difficult about the project, and its a very basic database, but i was just hoping to ask a small question.
I'm producing a DVD database, to hold details on a collection. My main table holds the majority of the fields, as follows;
lngDVD_ID
strDVDTitle
strYearReleased
lngDiscAmount
dtmFeatureLength
lngCertificationID
ysnBoxset
ysnExtraFeatures
strDirector
lngMovieStudioID
lngCategoryID
curPurchasePrice
The problem came with boxsets. Originally i was just going to have boxsets as one entry, but some contain a few dvd's, each with different certification, etc, and i wouldn't be able to record running length, director, etc.
So i added a ysnBoxset field (just to record whether a dvd was part of a boxset or not) and then made a new table with
lngDVD_ID
strBoxsetName
So now i can record which are part of a boxset, and the name of the boxset they belong to. But.. then i got to the problem of Purchase Price. Obviously i cannot record an individual purchase price for those which belong to a boxset, and i want to be able to record the price of the boxset.
So my question is... is it acceptable to add a curBoxsetPrice field to tblBoxsets, which would allow me to store the price... and then just leave curPurchasePrice as £0.00 for those dvd's in a boxset??? Or is there a better way of doing it? (I know there is, but i'm a novice :( )
Thanks for any help you can give, sorry for the lengthy explanation! :rolleyes:
Within my db I have a table, tblProjects which currently has 36 fields. Each project will have a fixed set of 12 tasks, each having a begin and end date as well as a yes/no "completed" field. This would add another 36 fields to tblProjects.
Instead, I have created a new table tblTasks which has these 36 fields along with a PK(TaskID) and FK(ProjectID) and is related to tblProjects. I believe tblProjects is already normalized properly with relationships to tblCompanies and tblContacts as well.
I'm not sure if this was neccessary, or should I have just added the task fields to tblProjects. What, if anything, are the advantages of one way over the other? I'll be upsizing to SQL Server, does that make a difference?
I appreciate any advice,
Sup
Hi,
Bit of a long one but I require some advise if people can supply it.
I've started creating a DB that is now getting out of hand due to me being inexperienced. The things I want to do now are getting way to complicated. From reading various posts I know that this is all being caused by my database design and while the DB is still young I'm go back to square one. I want your advice on this if you can to ensure 3 weeks from know I'm again not chasing up weird bits of VB code to make it all work.
I basically have a lot of information to hold that interconnects with each other. I'm making up a role profile DB (so we can assign define access rights to a computer system) I have lots of info to collate but the basic stuff is.
Staff Records (Name, business area & ID)
Applications (What computer applications do staff require)
Shared Drives (What access to shared drives and folders do they need)
Shared Mailboxes (what access to shared mailboxes)
Roles (users will be assigned roles to suit their requirements)
Basically what I have at the moment is below.
Roles
Role ID
Role Name
and about 15 other fields that dont really matter for this
Applications
Application ID
Application
Shared Drives
Shared Drive ID
Shared Drive
Shared Mailbox
Mailbox ID
Mailbox
Each role will only have a select number of applications, mailboxes and drives from the overall list. so role 1 may give access to 2 of the 10 applications, 1 out of 5 shared drives and 3 out of 4 mailboxes. Role 2 on the other hand may need 9 out of the 10 applications, 1 out of the 5 shared drives and 1 out of 4 of the shared mailboxes.
I just don't understand how I can create a form from these tables that would display all the different roles with their respective apps, mailboxes and drives they would need.
any advice you can give to help whould be appreciated.
Again sorry for the long post.
I am designing a db for our Law office. I want to have tables for different types of Civil Cases-ie Divorces, Deeds, Contracts, Personal Injury, Auto Accident, Slip and Fall, Product Liability, etc. The divorce, Deeds, tables are easy but I am having difficulty deciding on the personal injury tables. Heres my dilemna. Can I get away with one or two Personal Injury tables even though there will be blank data fields. For example, I will need a field for the name of the product in a Producrs Liability field. This field will be blank in all other Personal Injury Cases. I know the rule is you don't do that but my alternative is 15-20 tables for every concievable Personal Injury Case- Auto Accidents, Slip and Falls, Fraud, Prouduct Liability, Accounting, Attorney, Dental and Medical Malpractice, etc. This is in addition to other civil case tables, criminal case tables and federal case tables. Anyone have a suggestion?
View 6 Replies View RelatedI am not sure if which I should be using as the main entity for my tables. I am creating a database for hourly information on individual employees. Each employee will have the same types of hours to keep track of (weekly, bi-weekly, monthly etc) I naturally thought to treat each employee as the databases own entity and created fields for each type of hours but hit some trouble when trying to pull queries to compare each employees hourly information against each other to see who is being efficient or not. Each employee has the same exact fields but with just different numbers. We track each type of hour by week (Field One: Week 36, Field Two: Aug 28-Sep 03)This is the first time I am creating a database from scratch. All advice greatly appreciated and TIA :confused:
View 10 Replies View RelatedI have a table within a database and i was wondering whether or not i should split the table into 2 seperate tables.
The layout of the existing table is to record quotation information ie product codes, cost price, sell price, delivery dates available etc and it also contains fields that allow the user to state if the quote has been authorised or declined, when it was authorised and a number of options to explain the reason the quote wasn't accepted.
QuotationID - Primary Key
EmployeeID - Foreign Key
CustomerID - Foreign Key
EnquiryID - Foreign Key
ProductCode
Quantity
CostPrice
SellPrice
DeliveryDateAvailable
Notes
Authorised - Yes/No field Type
DateAuthorised
Declined - Yes/No field Type
ReasonDeclined
LostPrice - Yes/No field Type
LostStock - Yes/No field Type
LostDelivery - Yes/No field Type
LostCustomerClient - Yes/No field Type
LostNoFeedback - Yes/No field Type
above is the layout of the table, does anyone think that it might be a good idea to split this table into two tables, one table to record the quote information and another to hold the authorisation or decline information??????
i am creating a database for a local football club. I want to show player information (the main focus of the database), such as, what guardians are responsible for this player, what are the Doctors details for this player, what team does the player play for etc.
I have seperate tables for the Guardian, Doctor and Team information.
I also want to hold Staff details, (Name, address, staff title etc)
My problem is that someone in the staff table, could also be in the guardian table.
Should i combine the Guardian and Staff tables into one table as I dont want to have to enter the data twice for both a staff memger and a guardian
Note:
a player can have more than one guardian
a guardian can be responsible for more than one player.
What is the best way to approach the design of these database tables.
Thanks in advance
Pat
Have a database that I am working on this is constructed to perform Compliance tracking of wellness activity by employees. Have all my tables, queries and a form that has 3 tab controls as well as a subform on one of the tabs.
It is necessary to create a quarterly report card based on 6 wellness cateogories that have specific criteria. I thought I was OK but now I am having difficulty pulling it all together on the report. I now think that it has to do with my table construction and I am looking for advice. If there is someone I could send my DB to who can take a look and give advise or assistance I would greatly appreciate it. Thanks.:confused:
Hi,
I'm currently in an internship working solely with databases. I've become really interested in designing databases and I now want to design my own. I was wondering if I explained my table structure then someone could give me their thoughts and ideas for improvement. I have a huge sport trading card collection and I wanted to create a database for it. This way I could run some quick queries to find out how much my collection could be worth, how many cards I have, easily keep track of duplicates. Things like that.. This might seem strange, but I think it would be a good learning experience that would help me utilize many of the features of Access.
My Table Structure:
Ok I have a Company table(Topps, UpperDeck, etc) and they sell many boxsets(which would be another table).. Boxsets have many Cards(which would be my third table)...
Now here is where I get confused. I want have a sports table that would categorize my cards by what sport they are, but I don't know where I could link this. I also have a players table. This table will have a 1:M with Cards because 1 player can have many cards, but couldn't Cards and Players have a 1:1 because 1 card shows one player???
Finally, I want a Price Table that will be linked somewhere, but I've yet to figure out where to link this too.. Have I missed anything???
Your ideas and opinions are greatly appreciated!!!
Thanks!