I would like to use a Tab control to display the many side of a one-to-many relationship. However, I don't know at design time the number of records on the many side and was thinking of adding the number of Pages to the Tab control at runtime. But then I remembered that trying to change the design of a form needed exclusive access to the db. Has anyone successfully done this or might there be an alternative?
The one-side of the relationship has the customer details and the many-side are the details of the bank accounts for various currencies for that customer. A customer may only have one account for all currencies or a different bank and account for each currency. I was thinking the Caption of each Page of the Tab control would show the currency if there were many accounts for the customer.
Related
I am creating a web application but I am not very comfortable with database designs.
So user can only be an enterprise or an organisation, so I added a picture here with my idea. But is there a better way to deal with that kind of user types? Or there should be just two seperate tables (enterprise, organisation) with login credentials and etc.
Personally I would class an Org and a Enterprise as the same thing (Database wise) as you can see by looking at your columns. They are all the same except for register number but I'm sure Organisations also have a unique ID number.
If I was doing this I would have:
User m->1 Business m->1 BusinessType
Also should a User not belong to a Company/enterprise/organisation? The way you have it only one user can ever be associated with each. If you had the FK on the User side you could associate many users with one organisation.
I am new to access, and I am trying to make a simplae project of managing users.
I have a table of USERS, and to more tables of SERVICES and GAMES.
I have connections of ID in USERS, and ID -> USER_ID in SERVICES, as well in GAMES.
Now I want to display in one form, USER profile, and to print the games related to the user and the services related to the user.
I added a query, that joins with USERS and SERVICES and GAMES, and it shows everything right, except that if the user for example has two services and only one game connected to the USER_ID, then it prints the game twice.
is there a way to display it correctly?
in normal SQL and PHP, it would be easy, though in access I have no idea how to do it.
thaks
I would like to know if a microsoft access form can sort information into specific tables based on a selection made with a drop down menu.
For example:
I want to make a database for a group of workshops I am offering with a form users can fill out online. Each workshop has its own table to collect user information (name, email, address etc.) that I can use to create individual reports from for internal company uses. As the user information is the same for each workshop, I ideally want just one form that users can fill out and choose which workshop they want to register for using a drop down menu rather than having to create a registration form for each workshop. This form I would like to integrate into my webpage.
Can access use this drop down menu to record the data into the specific workshop table? Or would I need one table that gathers the information entered by the user that will then transer the data to the workshop specific table via table relationships?
Is there a better way? I have no programming knowledge and am curious to see whether Access can handle a project like this.
As a big part of your question is handling a web interface, you'd want to probably use a HTML form with an ASP.NET page(backend) to connect to the Access database, but make sure it's secure. I would read up on file permissions and parameterized queries.
To filter by workshop, as Marc B suggested, I would just create a column called workshop and have the value they selected going to that column. Otherwise, you'll constantly be creating new tables.
After searching around the forums I can find multiple issues with having several tables and one form, however I have the inverse problem. I have four separate forms that are all linked to the same table. No two forms edit the same variable on the table.
If people open up a single form, save it, close it, then move on to the next form the database works as intended. However, some people open up all the forms and forget to save/close the one beforehand. At this point, Access refuses to save the file stating that 'Another user has this file open' since the table is open in another form, even though no variable should overwrite each other.
Is there any workaround for this? I'd just like to have people be able to save their entered data from several forms to the same table. There will be no point in time that two people would access this table simultaneously, I just want to make sure we can save the data if someone opens multiple forms at once.
First, in a MS Access database multiple users can have same forms open. The only Read/Write issue would occur if users are working in the same record. Whoever enters the record first and begins updating would have the record-locked for him/her and users afterwards would get the warning message until the record is saved (or dirty event is removed). Users may be able to view but not be able to edit.
So your issue may be more an operational than a programming one. Try to organize users to manage specific records at a certain time or coordinate add/update work between team members. Of course this would be impossible if you run over a large company network with hundreds of users or online.
Still another solution would involve migrating all separate forms as subforms into one main form, so all corresponding records align at same time. But normally, subforms are reserved for join tables and not same table record sources. You can use tabs if space is an issue. This does not stop the record-locking issue but at least reduces the chances of it since less records are spread across separate objects. In fact this may prove to be better as users can move back and forth to other variables of the same record for reference on one form instead of opening/closing other forms or keeping the other ones opened.
Finally, it is highly advised if working in a multiple user environment and especially since you are connecting ODBC to systems like MySQL to split your database between FrontEnd (linked tables, forms, queries, macros, modules) and BackEnd (only tables). This setup prevents corruption, efficiently runs systems as only data is sent across the network and not whole application items, and overall fosters a better multi-user environment. Each user can have a copy of the FE on their local machines but all will connect to one BE on a shared network. To help, Access 2007-2013 has a button for this on the Ribbon under Database Tools.
I've used a dashboard that displayed buttons to open the forms needed and then used yourform.showdialog() to open up other forms in C#. This will make it so the user cannot use other forms until the form that is open is closed.
http://msdn.microsoft.com/en-us/library/39wcs2dh(v=vs.110).aspx
Does anyone have any pointers on how to go about creating a "wizard interface" using Access 2010? I need a sequential set of forms that will be capable of branching the flow based on answers from the user and data found in the database. I have used Access before for some CRUD/Reports type of applications, but in this case I can't seem to wrap my head around how to get started on such a complex machine.
Before anyone suggests it, I cannot use anything but Access due to client requirements.
I feel your pain ... working with Access gets so difficult where there are complex requirements.
Gather and document the requirements
Make sure you've teased out every possible wrinkle and contingency from the client, and put it into a flow chart or something.
Extract the models
Figure out what models are being used -- customers, addresses, vendors, products, etc. These will have to be created as tables or adapted to existing ones.
Extract other variables
What could potentially change over time and/or what will the client want to be able to change via an admin screen? You'll have to decide which of these variables to put into tables, and which are ok in the code (form logic and/or VBA).
Design the tables for the wizard views
I imagine you'll want a wizard screens table, where each row corresponds to a step; each should have (other than an id column) a previous screen column, and a form name or form template name column. You'll need a second table choices with a many-to-one foreign key linking back to screens; each row here will correspond to a possible outcome of the view, and the target next step in the wizard.
Design the forms
Finally, design the forms corresponding to each wizard step or template, pulling data from the structures in 1-4 as needed.