We have a split MS Access database. The front end was distributed among us. And some users are able to run queries and edit query results without a hitch. But a few others are not able to edit the query results. The query runs fine for them and they are able to see the results in MS Access. But editing any field is not possible.
Could anyone advise me on how this can have happened. I have primary keys on all the tables on which the queries are based. And there are no joins in my queries. Each query runs on a single table.
Thank you in advance for your time and help.
With regards,
Manus
I got the answer. The back end database was on a network drive where some of the users had write access but not all. Silly of me not to look there first. So basically the users who couldn't edit were the ones with no write access on the shared drive in which the back end of the database was kept.
Related
so i am trying to pass time during the end of the world learning a bit of access (i already know a decent bit of sql). I am particularly interested in pulling query results made in access to use them in excel.
So far i have managed to create my database in access, populate it with data imported from excel and create the queries i need to use in excel. I have also managed to get the queries data in excel using MS Query (from "From other sources" menu because i would to query the query with parameters) and it is all peachy. It fails when i upload the access database on my work network. For some reason i can access the tables but as soon as i try to load my access query in MS query, it will just freeze to death.
I tried letting it run 20 minutes to no avail. I was wondering if anyone ever had that kind of issue. i tried several things for example i can access queries from other online database, the difference is that database is less heavy (the failing one is 100 mb) but considering i m a beginner i am not sure what else to do.
Thank you in advance
edit : i left it running and apparently it works, it's just that it takes a gazillion years : it is a sum query that runs on a 900k rows table
SELECT main.yearData, main.period, main.week, main.articleId, listArticles.brand, listArticles.description, groupToType.type, listArticles.model, listArticles.color, Sum(main.sales) AS totalSold, Sum(main.stock) AS totalStocks
FROM groupToType INNER JOIN (listArticles INNER JOIN main ON listArticles.articleId = main.articleId) ON groupToType.productGroup = listArticles.productGroup
GROUP BY main.yearData, main.period, main.week, main.articleId, listArticles.brand, listArticles.description, groupToType.type, listArticles.model, listArticles.color;
Is there anything i can do to make it run faster? i cannot wait 15 minutes every time to get the update info.7
Thank you again !
I'm implementing my first Access Database. I've read numerous guides/manuals, and I believe I'm nearly at the finish line. The Access Database will be used by 3-4 users.
I have three tables, all of which are "live" connections to three different Excel file. These Excel files are on a shared drive, which are to be updated periodically by the different users.
I have a single query that uses each of the different tables (3).
The goal is to give the users the ability to view the output of the query. From my understanding, the best way to structure Access is to split the database. I'd like the three tables to be stored in the "Back-End" database, and the Query to be on the "Front-End" database.
The issue that I'm running into is that, when using the "Database Splitter", I'm given the error "There are no tables in this database. The back-end database will be empty". I've searched for the past couple hours, but I can't seem to find a reason for this error. I believe it is quite clear that I do indeed have tables. What am I missing? Any input/suggestions are greatly appreciated!
The "Database Splitter" can be used when you have tables and front-end things in your database. The "Splitter" would then create an additional Access database, "move" the tables to the new database and create linked tables in the old database that map the the tables in the new database. You already have linked tables, so there's nothing to split (your linked tables are not even Access tables).
I am using access 2007. In the database I am using a delete query to remove data from a table. What shocks me is that even though I have create multiple duplicates of the database in several different locations and with different names on the same server PC, the minute I run the delete query it removes all other tables on the other databases which I do not wish for as they are backups.
Could someone please help to explain why my delete query is not limiting itself to one database.
Thanks
Found my answer. The database was broken up into a back and front end. Making duplicates of the front end still was linked to the original back end. Had to copy over tables from back end to front end to make the database a single entity again.
I'm a java dev who uses Mysql Workbench as a database client and IntelliJ IDEA as an IDE. Every day I do SQL queries to the database from 5 up to 50 times a day.
Is there a convenient way to save and re-run frequently used queries in Mysql Workbench/IntelliJ IDEA so that I can:
avoid typing a full query which has already been used again
smoothly access a list of queries I've already used (e.g by auto-completion)
If there is no way to do it using Mysql Workbench / IDEA, could you please advise any good tools providing this functionality?
Thanks!
Create Stored Procedures, one per query (or sequence of queries). Give them short names (to avoid needing auto-completion).
For example, to find out how many rows in table foo (SELECT COUNT(*) FROM foo;).
One-time setup:
DELIMITER //
CREATE PROCEDURE foo_ct
BEGIN;
SELECT COUNT(*) FROM foo;
END //
DELIMITER ;
Usage:
CALL foo_ct();
You can pass arguments in in order to make minor variations. Passing in a table name is somewhat complex, but numbers of dates, etc, are practical and probably easy.
If you have installed SQLyog for your mysql then you can use Favorites menu option in which you can save your query and in one click it will automatically writes the saved query on Query Editor.
The previous answers are correct - depending on the version of the Query Browser they are either called Favorites or Snippets - the problem being you can't create sub-folders to group them. And keeping tabs open is an option - but sometimes the browser 'dies' - and you're back to ground 0. So the obvious solution I came up with - create a database table! I have a few 'metadata' fields for descriptions - the project a query is associated to; problem the query solves; and the actual query.
You could keep your query library in an SQL file and load that when WB opens (it's automatically opened when you restart WB and that file was open on last close). When you want to run a specific query place the caret in it's text and press Ctrl+Enter (Cmd+Enter on Mac) to run only this query. The organization of that SQL file is totally up to you. You have more freedom than any "favorites" solution can give you. You can even have more than one file with grouped statements.
Additionally, MySQL Workbench has a query history (see the Output Tab), which is saved to disk, so you can return to a query even month's after you wrote it.
Am trying to import some selective data and create a table in MS Access db 2002 from a linked table. For some odd reason the performance became really bad all of a sudden when importing the data.
I tried googleing and tried various methods like reparing/compacting the db, Changing the SubDataSheet Name to [None] from [Auto] but either one worked.
Can any one please give me some examples to increase the performance of linked tables.
Thank you.
Rather than selecting information from a linked table and trying to make a local table, when using a database server like MS MSQL, you would be better to create a "Pass Through Query" to do the select work on the server side, and then carry out a simple select * on this pass through to get your data in to a local table. This will give the best results if your first select statement is complex and takes a while for Access to run on a linked table, if that is not the issue then you will need to look at your network speed which connects you to your MS SQL server.