Ok a bit of back ground. I'm building a access front end to a sql database. The end user will access the information in the database via asp pages on the Internet. They will only be viewing and not changing this information.
Now from the asp will be links to other pages within the same site. So they only have to be relative links eg .../folder/page.htm. But I want the person who inputs the information in the access front end to be able to test that the link works before saving the record.
I would prefer them to be able to press a button, then have access grab the link from the text box, add the relevant other bits eg http:// and load the page.
I wonder if someone can give a suggestion on how to start this database. I am doing a material list database, but i've come across a situation where certain materials require a lot of text entry as opposed to some of the others where you simple enter data such as " density, grade, strength, etc" values. Because the layout/fields would be so different for the different materials (eg. plastics, metals, elastomer, etc.) it possibly might be a good idea to just separate them into different table groupings altogether? what do you think? Originally they were entered in Word and i was thinking of putting in access to standardize it. But what I'm trying to get at is the format in word was much like a one page report with headings and short paragraphs for this section of materials. Is it worth it and how should I go about having large text and heading entry, form use, report layout? Thanks!
I am starting a new database today at work. I need some suggestions.
First of all, we will be having people enter data into many sections of the database at the same time...should I create seperate databases for these sections and link them together somehow so that it doesnt freak out with multiple users or being saved while open in different computer on the server?
Will it freak out anyways? What happens exactly if you open same database on two different computers.
Next, I would like to know if anyone has any further ideas about creating this database the right way in a server setting with multiple users!
Hey all, I am currently looking to make a great database system for use within my community. What I currently have is a mdb with just 3 tbls but will be building from there. I have the normalization down thus far, but wanted to put things out there for any suggestions or ideas to make this a useful system. This is not a profit situation, and will generally be used only by myself or possibly one or two others.
What I have is a database that tracks the homeowners within our community (subdivision) and their properties. So far I have 3 tbls
Structurally this works great so far. I can easily relate properties to their owners and link multiple properties to those who own more than 1 (landlords). I structured it this way since the two tbls had many to many relationships, so the junction tbl made the most sense. Now I am looking to add information from a tract search (mortgage holder information) which technically relates to both of these tbls (Unit & Owner) as well. I already know that most of the owners with multiple properties will most likely have the same mortgage holder, but that is not definitive. Since the same mortgage holder could easily be associated to multiple properties within the community, I know I have to have an independent tbl for that information as well. What I would like to head for is something that will allow me to send notifications, letters, flyers and the likes to either the owners, residents, mortgage holders, or any combination of the three. I have attempted to create a few thus far but have issues with getting all of the required data output to Word, so I am thinking I may need to design these items in a Form instead.
Any thoughts or comments would be appreciated. I know I am heading in the right direction, but just putting it out here for the Access community to put in their 2 cents.
Hi, I'm afraid I am unable to be overly technical with my question as i've only really had a 2 day access course, sorry in advance!!!
Problem I am trying to create a skills Matrix, it will need to include approximately 400 different skills which a staff member my or may not be trained on. I started by trying to do the lot on one table and an one input form but hit the 255 field limit. So now i'm messing around splitting it down into approx 7 sections. So, now i have 7 tables of skills and 7 input forms for the user to fill the table with, each table with a duplicated list of ID numbers for the staff. This seems really inefficient to me and i'm basically wondering if someone might give me a couple of tips structure wise. Also, could i just have one table for the staff ID's seperately? I tried to do this but cannot find a way of relating the skills input on the form to the specific ID if they are not on the same table. I know this is all probably really basic (and probably poorly explained and confusing too) but i've scoured the net as per usual and came up with nothing (i got some lovely code online which disabled the scroll button from moving records yey! :p ), so ive taken the brave step of joining a forum. Thankyou for your time everyone.
I have a databse that i want to perform some analysis on to identify some trends. The database consists of album sales of a year. I have availble all details of orders, customers and albums. All tbales are joined with one to many relationships. Can anyone suggest some queries that i could do to perform some meaniful analysis to identify some trends in the data. :confused:
I am developing an app for a small medical office that requires a way of tracking periodic health testing for their patients. They are ultimately requesting a report that informs them of upcoming required tests for their patients.
Most periodic tests for a given patient will be manually assigned by the user in the frmPatient form via a combo box that lists available tests (for example, Mr. Smith is assigned a prostate exam with a frequency of every X months). However some tests need to be automatically assigned depending on the age of the patient (for example, when a male patient turns 50 years of age he needs to have a prostate exam every 12 months).
My Question: What is the best approach to the automatic requirement of adding/flagging/indicating in a report that there are tests that are needed for patients that is determined solely by their age, eventhough this test has not been previously assigned manually?
I needs some advice on how to proceed. Our company is devolving some operations to a sub office for 3 out of 11 business units. we have a central DB that we use to record monthly events the problem is that the parent group has to be able to update records for all units but the sub office is only allowed to see and edit their records
At the moment the data is all stored in one table and we use a Front end back end with local front ends for access I have a table to say if a unit is part of the sub office or not and in the sub office front end i have a Query which links the 2 tables together and filters the records to show only sub office
SELECT tbldatatable.*, tblShipName.Manager FROM tblShipName RIGHT JOIN tbldatatable ON tblShipName.ShipName = tbldatatable.Ship WHERE (((tblShipName.Manager)="nv")); the remainder of the forms and querys all run from this query rather than the tables
the problem is the join makes it a non updatable record set
what is the advice on how to achieve what i need as i cant see a simple way to proceed thanks ND
I'm creating databases that houses information of the different software versions my company offers. This way they can easily keep track of updates, obsolete info, etc.. I'm trying to decide what way would be most benifcial. I've been leaning more towards creating multiple databases and having a dropdown box in the beginning to open what database(version) you would like to view. Is this the only way, or does anyone have any suggestions on how to make my idea better?? Just trying to Brainstorm, also, I'm only an intern so my experience is limited.:D
I am creating a database where the user can import data from a number of spreadsheets (one spreadsheet for each company). Currently I have one table for each company with the year being the primary key. Each year when a rolled over spreadsheet needs to be generated for a certain company I have Access import the data to a blank template in excel which will display the prior 4 years of data (for informational purposes) and leave a column blank for the end user to fill in the current year data. When returned the current year data is imported into the database.
My problem is that I cannot see a way to do this without having a seperate table for each company. If I have one table with all company data I cannot use the year as the primary key. Any suggestions on how I can reduce the amount of tables I need. Setting up the rest of the tables wont be a problem, but future users of the database will have to go through the process of creating tables for new companies and creating all the queries and macros associated with that table.
I am converting a log book over to MS Access. The log book contains information on inspection results for a metallurgical lab. I have one problem w/ my “inspection table” which I will explain later in the post.
This is the plan I am using to figure out my entities and attributes for the database. I wrote a short description about the hand written log book we use at work.
A log book is an array individual fields. Each field is made up of 11 columns (date, initial, log #, sent to customer, customer, dept, part #, load #, results, acc/rej, and defect code).
The date pertains to the time a particular part was inspected. Initial indicates who checked the part. Log # starts at “1” Jan 1st and increments for each check throughout the year Sent to cust asks if “inspected” samples are sent back with finished product. Customer displays owner of finished product. Dept indicates the processing area of plant. Part # distinguishes the part type. Load # may display what furnace and run count for the year to date. Or, tub number in an array of tubs processed through a continuous furnace. Results give a list of values on test results. Acc/rej is a simple “yes/no” question asking if finished product is acceptable to ship to customer. Defect Code represents a particular defect found during inspection
One problem with the Inspection table; we have different inspections for each part number. Some require 10 RC punches others only require 5 RC punches. Some Require a Total Case inspection. Others Require an Effective Case inspection or both TC & EFF Case.
Some part #s require all tests (i.e. Crush, Total Case, Effective Case, RC, & R15N)
Once I figure out the basic table setup I can use a query to build the final log. And develop a forum for the data entry. I’ll worry about the CPK reports later :)
Here is a sample database Let me know what you think. I still need help on the INSP table :) Your Download-Link: http://rapidshare.de/files/10087240/SampleTable.zip.html
I have almost ultimate my database which works with forms that export their data to word documents.
The code behind the forms indicates that path to which it will find the word documents.
As I will be sharing my program with several offices, I will need that each Office will have to change the path based on their server name.
Examples of path: \ABC123shared emplatesmydoc.dot
Is there a way each office or better on person which will be the database administrator can change the ABC123 in all forms without having to open each one in design view and manually make the change?
I was thinking of some kind of text box where to write the path and a cmd that will do it for us.
I have a products file in csv format including their category, subcat, and brand name.
Now I want to take that file and split it up into 2 tables in Access. One table will contain the product data only: name, description, price, etc, etc - with a primary key (of course) and a category number. The 2nd table will be the categories for each. The formatting of the categories table needs to be: Code:Cat ID | Category Name | Parent ID 1 Tools 0 2 Hammer 1 3 Pliers 1 4 Hardware 0 5 Nails 4
Does that make sense? My real problem with this is finding a suitable number format for the categories. I imported the file as a table, then I run a query on it to get the ID's for each of the category, subcat, and brand, but of course in the above table format I'll end up with duplicates. Also, how would I then assign the final number to the product itself?
I have just about finished up a Split DB that I plan on deploying in a LAN environment. The goal of course is to turn what looks like an Access Application now into a non-access looking application where the Front End can be distributed and run on any computer within the LAN.
I have several questions that I may need some help on.
How does one go about hiding the Access Shell and/or Ribbon/Nav in 2007?
How would I add a form that allows for a user to navigate to and connect to the back-end without having them check all of the appropiate tables and then browse to the back-end file if they have a different drive letter mapped to the location of the back-end files for example?
Any tips on how to sign the DB so the pesky Trust Center question can be bypassed?
Any other tips on how to simply distribute this for a LAN environment and/or make it look NOT like an Access DB with access to view the Forms, Tables, Queries, etc. This is my first Access DB project, let alone a LAN distributable one.
