Dear All,
is there any way to look-down the structure of tables within a database so users cannot change tables?
Is it possible to make this password protected so only certain users have rights to change the layout of the tables?
Would this still allow users to create queries and enter data?
Thanks, Steve
I have a company wanting to asses my database and i am willing to show them but i need to be able to lock the database so that they can view it but cannot edit anything in it either adding deleting or plan editing. How can i do this.
Bullfrog
The Amateur
Hello,
As my username states, I am a rookie to MS Access. I built a database using Access 2002, I will distributed it to other people, I will like to lock changes to certain areas such as forms, design view, etc.
Can this be done? The help is greatly appreciated!
Rookie2007
I have looked on the forums and cant quite find what im looking for so i wanted to ask you lot for help.
I have a database i have created.
It will be sent out to people to populate via a series of forms i have created.
How can I lock it down so that:
1) you cant access any of the database apart from the forms
2) Lock it so no one can get in to view the code anywhere or make any amendments to the forms and database what so ever
I am new at this stuff. So please excuse my ignorance. I created a database which a lot of my colleagues want a copy. I don't mind giving them a copy. However I don't want them to change the design or copy it to give to others. I don't mind them adding their records.
Is this possible to do? Or should I just keep the database to myself.
Thanks in advance to your advice.
I have prepared an access database on a shared drive location(lan) with 5 tables. The main table has over 110 fields and is linked to a form. On an average the table stores 12000 records, which are updated via a form.
Normally, 7 users work on this form and do add/change/delete operations on the records.
The frequent issues I face are:
Corruption of records.
"Could not update, currently locked" errors.
I have constantly tried compact and repair option, but the same does not give required results.
Kindy advise a solution.
Does anyone know how to lock a database so it can be accessed by only one person at a time? We have several users using a 'local' copy of the same database and frequently synchronizing with a network copy. We want to avoid a situation where more than one person is trying to synchronize with the master. Please advise - thanks!
View 2 Replies View RelatedI have a call tracking database with 5 active users. Ocasionally the database will freeze, usually for several people at once. It will say:
"Can not update record; Currently Locked"
The only way to fix it is to close and re-open. I split the database, compiled it and then created an MDE file to distribute. They are using copies of the front-end, not links. The database locking more and more every day. But we are using it more. After parusing the forum I'm starting to suspect that this is a problem of "Primary Key duplication" If everyone trys to create a record at the same time, would the database lock because we all created the same record at the same time?
If so, how do I get around this? Use something other than Autonumber for the primary key? Or is this an entirely different problem?
By the way, my record locks are set to "No Locks"
Thanks!
Have an Access database that is used by multiple users, the lock file seems to have vanished. Yet the database is in a read only state and still locked. How do I unlock the database? How do I find out who is locking it? How do I kick the person off is neccesary to unlock the database? Thanks.
View 5 Replies View Relatedwhy is it that as soon as you fix one problem another one needs dealing with :mad:
OK, the problem i have is that i have a BE/FE configuration database in a multiuser environment. I have built all the tables and the relationships in the BE configuration. In the FE configurations i have built the main forms to input data. It has no come to the point where i have begun to create the queries to allow reporting and data searching. And this is where i have a problem. I am trying to create a simply query and i do mean simple (at the moment i simply want 2 fields from 1 table and 2 fields from another table) no calculations or anything i just want it to display the data. I have tried creating this query numerous times and i keep getting the same error.
"The wizard is unable to open your query in datasheet view, possibly because another user has a source table open in exclusive mode. Your query will be opened in design view"
the above is the error i get when i use a wizard to create the query, after getting this message and going into design view i try to view the results in datasheet view and get the following error "Type Mismatch in expression"
If i dont use a wizard and create it in design view, when i go to view the results i get the second error message everytime.
If i create a query from 1 table only the query works without errors, but i always get errors when i have more than one table in the query.
Also i am the only person with the database open so therefore it is total impossible for the database to be open by another user in exclusive mode.
Anyone know what the problem might be or how to fix. Your answers will be very much appreciated.
Another baffling problem - there are far more traps for new players than I ever imagined. Any suggestions gratefully received.
I have a fe/be split database with multiple users on a network. All users have the same front end on their PCs and are either running Access 2000 or 2003.
Problem 1:
Some users cannot open the database at all, getting the error message "Could not open xxxxx.mdb - File already in use."
Problem 2:
Some users can open the database but get a message in the status bar saying "Recordset not updateable."
Other users, running either Access 2000 or 2003 have been able to use the database without difficulty. The number of users is in single figures and it is unlikely that more than 4 people have attempted to log on simultaneously.
The database default open mode is set to "shared", the default record locking is set to "No locks" and the "Open database using record-level locking box is checked".
I have been having difficulties setting the security for the database (see other postings on this site) and so it is currently unsecured with no password set for the admin user. Users are joined to their default system Workgroup Information Files.
My guess is that there is a setting on the Access installation of the user's PC that needs to be changed but this is only a guess - anybody any idea what I should try next?
Regards,
Keith.
I have created two DBs, one Back End, and one FrontEnd. My FrontEnd contains all the UIs/Forms, Linked Tables, and the queries fetching data from linked tables, and the Back End consists of all the Tables.
Now, in my Model, the BackEnd DB will be stored in a common drive and will be accessed by multiple users through same FrontEnd.
Now when I am trying to fire a query in FrontEnd (aka FE) DB, it is locking up the Back Up database. Even though I have set the RecordLock property to No Locks to query and the form.
how to remove the locking?
Is there any way to keep track of a database structure in access? For instance, which query relates to which report? Sometimes I create queries that are no longer needed but if there are a lot (which there are!) it can be easy to delete one that's needed.
View 5 Replies View RelatedI created a database to track tardies and absences of my employees. I would like to be able to sum the number of absences and tardies for each person per month and graph it.
Per our attendance policy, 6 tardies = 1 absence. I need to take the total number of tardies that month/6 and add to the total absences that month to equal the total attendance for the month.
I need help. Can you please view my database and give me some ideas?
Thanks,
Jason
I am designing an application that tracks information on Choir membership and sheet music that we have on file. I am starting with a database of church members. There are four different choirs and choirs share some members. Some members of some of the choirs are also not members of our church so I will have to place non members in the member table. I am new to database design and would like the collective wisdom of this list to tell me of any problems I may encounter before I start doing any detail work.
What is the best way to deal with someone who is a member of more than one choir and may belong to a different section in this other choir (Tenor in one and Bass in another). An individual may also hold different offices in various choirs.
The table structure I have is as follows
CHURCH MEMBERSHIP DB:
MemberId Autonumber (pk)
FirstName, Text
MiddleName, Text
LastName, Text
DateJoined, Date
Phone, Text
Address, Text
City , Text
Zip, Text
EmailAddress
BirthDate, Date
Member, Boolean
CHOIR MEMBERSHIP DB (How do I efficiently track someone in > 1 choirs)
MemberId, FK
ChoirId, FK
FolderNo
RobeNo
Section
ChoirOfficeId, Fk
CHOIRS DB (This lists the various choirs in the Church)
ChoirId, pk
ChoirName, Text
DirectorId, FK (Pointing to Member DB, Person may not be member of any Choir)
MUSIC DB
CatalogId, PK
Title
Composer
Arranger
Type (Single Copy/octavo or book/collection)
PublisherId, FK
PublisherNumber
VoicingId, FK (From table with possible voicing)
NumCopies
UsageId, FK (Where in the service is it appropriate
Location, Text (Where in the filing system, or off site)
ClassificationId, FK (List of classification/genre in table so can update)
PUBLISHER DB
PublisherId, PK
PublisherName
PublisherAddress
PublisherPhone
PublisherWeb
PublisherContact
MUSIC CLASSIFICATION DB
ClassificationId, PK
Classification, Text (Christmas, Easter, general anthem etc)
To be able to track performances and plan services and performances I have the following table.
PERFORMANCE DB (This is to keep track of and plan the regular service)
PerformanceId, PK
Pdate, date (Date of Past/Planned performance. Possibly more than one per day)
ServiceTypeId, FK (From table of types of performances – morning service, evening, etc)
Location
Speaker
Pianist
Organist
Introit
Invocation
Anthem
Meditation
Benediction
(etc)
I would also like to be able to prepare mailing labels for the various choirs as well as the general membership from this DB. My primary focus will be on the music. I would like to have an efficient music DB that I may find out what music I do have and when I last performed them, what options for performance (usage and classification)
Would be grateful for your comments, Thanks!!
Rmiller
I am trying to figure out how to store data into a database to be use later in a web app. So I have a shirt and it can come in four different colors. What would be the best way to enter this into the database. I'll have shirts, jackets and accessories which I have give each their own table. The shirt one is giving me trouble though, I just don't know how to organize it.
Thanks for the help
I have access BD and every one use it through shared folder. My problem is in attachment ! , if i use the regular attachment filed in access there is one user only able to attach files and others can`t attach any thing until he finish.
I tried to do attachment through VBA like below which make it worse as it lock the DB so, no one can even open the DB and one user only access the DB .
Dim db As DAO.Database
Dim rsParent As DAO.Recordset2
Dim rsChild As DAO.Recordset2
Set db = CurrentDb
Set rsParent = me.Recordset
[Code] .....
How multi users attach files at the same time without locking the DB.....
I'm doing some changes to a database in work, but the person who created it doesnt work there anymore and so nobody knows anything about it. The database has been split into a front and back end, which is fine, but there appears to be 3 seperate databases linked to the main one, each with a .mde file for security. Depending on which department you're in, you access your database. Any information being added is updated in the main front end database. Does anybody know how that will be linked? I'm just probably going to have problems when encorporating my changes.
View 5 Replies View RelatedHello,
I am looking for someone's professional opinion to help me clear up some unresolved technical issues in my mind... =P
Ok, I have a contact management database that would seem really straightforward to me except for the fact that I am dealing with 2 primary entities. In this I mean I have an Individual table and Organization table. These two tables have primarily the same field data, such as both having address data, phone (contact info) data. There are some unique fields to one entity that aren't contained in the other entity though, and visa versa. One important issue is that 0, 1, or more individuals can be related to an Organization. Therefore I now have linking tables for IndividualOrganization, as well as linking tables for Phone and Address data.
My primary complication is that since both Individuals and Organizations have address and phone data, the respective linking tables for them contain: an addressID/phoneID key, for the appropriate linking table, with an OrganizationID key and an IndividualID key in each table. So, the way I am thinking is that if the record pertains to an Individual, the appropriate ID will be in IndividualID and the OrganizationID will just be 0, or empty. This brings up issues with primary keys being blank.
I am wondering if there is a better way to do this that I am overlooking or if I am in fact on the right track? I have contemplated combining the Organization and Individual tables into one but that really doesn't seem like the best solution. If anybody has any ideas then I would GREATLY appreciate it. I had a working database the other day but now I am separating the phone and address info out of the primary tables and have really got a mess on my hands. =P If anybody would like to look at my database structure I'd be more than happy to post the back_end and the front_end for you to give me your honest opinion about any trouble areas.
Thanks BIG TIME in advance to any nice souls willing to help out a struggling programmer who doesn't have any close support on this one as I am working alone, :rolleyes:
Dana S.
I have 7 tables:
Booking - BookingID
Course - CourseID
Company - CompanyID
Materials
Materials_on_course (had to have this in order to avoid many-to-many.)
Employee - EmployeeID
Employee_runs_course (had to have this in order to avoid many-to-many.)
I'm stuck with the Course and employee thing. Each employee has an expertise or two, and therefore each course has an expertise needed to run it (a specialist if you like).. so the PK in 'course table' is Course ID, you cannot have two PKs in one, so would it be right to say that the 'expertiseID' would have to go in 'Employee_runs_course' ?.. what would i do then? place 'expertise ID' as an FK in both employee and course tables?
Extra info:
Clients (tblCompany) can book one or many courses
A course can have one or many bookings made for it
A booking has one or many employees/courses
An employee can work on many bookings (obv if available)
Each employee has one or two expertise (usually only one)
and therefore a course has on expertise attached to it.
__
If you have a better way of designing it, shoot!
Attachment: ERD (kinda) of first draft.
Hi People,
I am building a database of in-car audio systems. Stored in this are simple things like vehicle information, audio brand and other general information. The main information I need to store includes details about speakers (position, quantity, material, range, size etc.) and amplifiers (power output, no. of channels etc.). Sounds simple I hope.
I have been thinking about this extensively and have come up with two solutions, each with its own pros and cons. My primary concern here is how the speaker and amplifier information is stored:
1) Tables specific to car regions (e.g. Rear Speakers, Front Speaker, Surround Speakers) have the fields 'Range', 'Material', Size, etc. Range and material can read their values from other look-up tables no probs. These would be linked to the main table via it's primary key in a 1-M relationship.
-Pros:
Ease of construction and general handling of data
Flexibilty/expandability (in terms of speaker quantity)
-Cons:
When it comes to data entry the form would need to be continuous and continuous forms I have found to be a pain in terms of referring to individual records!
I want some of these controls to conrol a diagram for my report (and input form) - such that they show/hide speaker pictures on a car diagram. Also, I have not yet figured out how to validate a continuous form in this situation or delete records from it either (should the user makes an error).
2) Again, tables specific to car regions but this time with a field for each speaker range (mid-range, tweeter, woofer, etc.) and it's associated data, tied to the main table via the main table ID in 1:M relationships.
-Pros:
Easy to manipulate form/report properties because every speaker has its own field
Easier to remove erroneous data (I imagine)
-Cons:
More complex construction (and less efficient) - e.g. material occurs more than once for each record so to look up material form a central pool requires an intermediate table
Many many more fields!
Non-expandable in terms of speaker quantity
Similar principals can be applied to amplifiers so I haven't mentioned those.
So what do you think? Or is there another way...
Hope that all makes sense!
Thanks for your time,
Bobadopolis
Hi ,
I am developing an access application that will be used by our Marketing Dept to create BRIEFS for our AD agencies.
The Brief has the following structure
1. Option1
1.1 A1
1.2 A2
1.3 A3
1.3.1 AA1
1.3.2 AA2
1.4 A4
2. Option2
2.1 B1
2.2 B2
2.2.1 BB1
2.2.2 BB2
2.3 B3
2.3.1 BB3
3. Option3
........................
........................
........................
The users will be basically selecting from a list of Categories,Sub Categories and Sub-Sub Categories.
I am a bit confused as to what kind of Database Structure should I use for this kind of requirement.
Right now I have a table tblBRIEF that conatins the basic information about the BRIEF like
Project Name
Company Name
Date
Responsible etc etc
My question is , where and how should I store the selections made by the user for each of the Categories , subcategories and su-sub categories.
Should I have a table for each of the Categories and Subcategories and have a relation with the BRIEF table ???
You advice will be apprecaited?
Access 2000: How can I populate a two field table (1. Table Name 2. Field Name) with the name of ever field within every table in my database using VBA code?
Regards,
Dalien51
Hi all,
This is a fairly simple one, but im not sure exactly how to go about it...
Lets say a Company can have many Divisions. Each Division has 1 Division Manager (CGM), and manages many Cost Centres.
Each Cost Center has 1 Cost Centre Manager (CCM) and employs many Employees.
Im thinking of 3 tables:
Divisions, Cost Centres, and Employees. And if you hadnt already guessed, CGM's and CCM's are part of the Employees Table.
What is the appropriate table structure and relationships?
Thank you in advance...
I would like to build a database to keep track of tardies and absences in my dept (~70 employees).
I need Date, Name, tardy or absent,
My current table:
TblEmployees
EmployeeID PK
Last Name
First Name
Team
TblEvent
EventID PK
Event (Tardy or absent)
TblAttendance
Date
EmployeeID
EventID
Is this a good structure? I need to be able to run a query that will sum the total number of tardies and divide by 6. That number will then be added to the total # of tardies. The query needs to only show the values over the last 6 months.
Any help is appreciated.
Thanks,
jason
Hi i have a quick question
Lets say u have a database that keeps track of all items sold and their respective prices. So u have a items table that keeps the product information and price. Then these items are displayed on invoice kept in a invoice table linked with a foreign key and a one to many relationship.
My question is lets say the price of an item should change....will the invoice table of old invoices display the new price or old price. Is this where the referential integrity comes to play ? Should u select it when doing the relationship ticking the cascade update related fields and cascade deleted records boxes respectively or not ?
Anyone have any views on this ?
Ur help will be much appreciated
Kind regards
Frans