Search results
-
M
open form as read only but allow filters
Yes that could work but I use this form couple of times with different preferences so can't do it. Any other possibilities? -
M
open form as read only but allow filters
Hello, I have a button that open a form DoCmd.OpenForm FormName, , , , acFormReadOnly form opens as read only and everything is as it should be. In the footer of this form I have filters and I need to be able to use them. Is it possible to have form opening in read only for... -
M
Query duplicates data
HiTechCoach, Hi, have you had any chance to look into this database please? -
M
Query duplicates data
1. Thats the problem I am trying to resolve - I dont know why it doubles record count... 2. Task basically a job to do in specific location - in Area Each area has several machines in it, i call them all Equipment Dont know about subdatasheets... :/ 3. same as point 1. I dont know why it does... -
M
Query duplicates data
the query shows all records from table T_task. In fields where there was a number as foreign key, it is replaced by actual text from assigned tables so user can see useful data not just numbers. -
M
Query duplicates data
I hold the shift key down then double click it and hold it until you see all tables, queries and forms on left pane. When you open first time you had to enable content, then you need to close the DB and open again with shift please. When you open it and as you say it takes longer, its because... -
M
Query duplicates data
As I mention in previous post: the database has menus and options disabled unless you open it holding SHIFT key. Then look at design of query: Q_task, there is 480 records, but when I add table _Area to the query it multiplies all records and gives over 3000 records. I dont know where is... -
M
Query duplicates data
When you open it up. On right hand side there is a TRACKER button. A form will open in data sheet view. The query it's based on gives me too many records. The query duplicates records. I can't work out why. This is where I need someone's help please. -
M
Query duplicates data
yes thats right. I have made a mistake, yes user would always associate a task to an incident. ex: Incident: Toxic liquid spill on the floor Task: Clean up & ensure floor surface not damaged. Yes. Yes t might seems like repeated, but they are not, so user need to enter task description... -
M
Query duplicates data
1.An incident - something unusual happened in an equipment and user has to report it. 2.User reports an incident, and can add a task where he/she will enter something like: John has to inspect electric motor in area where incident happned. 3. I guess so, You report incident as a new... -
M
Query duplicates data
No. Incidents can have tasks. You created an incident there is a subform you can add a task. When you create a standalone task, you have a separate form that's all you do just create a task and add department and area and user. -
M
Query duplicates data
Yes to all of your questions. Yes T_qa is incident collector and T_task is a task collector Incident can have many or 1 or none tasks assigned to it. Also need to be able to add a task for AREA not related to an incident. -
M
Query duplicates data
Table T_qa is the main one, it has field T_dept, where user selects department of incident. then based on this selection user will select a UserName and Area and Equipment. 1 department can have many areas. 1 department can have many users 1 area can have many equipments 1 record in T_qa can... -
M
Query duplicates data
Yes that's right T_qa is my incidents. I think I need some kind of relationship between t_qa and department and area and equipment as I need to know location of an incident. But then I also need T_task to have relationship with table department and area for my non related to T_qa tasks. I'm... -
M
Query duplicates data
Yes thats right, you got it. I'm sorry, I don't understand. Do you mean create an incident as a table or as individual records as I am doing now? Why different types? I don't understand the purpose, sorry, can you explain this to me please. Please see below full structure -
M
Query duplicates data
Ok, the database is a tracker. We track incidents across few departments. Each incidents has a location: -department -area -equipment Then also person reporting -user (from the selected department) Then each incident has an action hence table T_task And that was it until few days ago. And now... -
M
Query duplicates data
Oh I understand, Yes you are right. No I don't need it for report (not just yet), it meant to be just to display all records for users, so they check it everyday and if task has been completed then they will tick a checkbox and/or add comments. I've decided on current relationship design...