TableC as much as they want, for a certain period of time. UserA and userB can make changes to their individual tables tableB and When they push from tableC to the MySQL database, they create tableE, which is the differential between tableA and tableC. userB pulls from theĭatabase and makes changes (creates tableC). Then then modify the table (create tableB) and push the data to a separate table tableD (where tableD is the differential between tableA and tableB).
userA pullsįrom the MySQL database into the Excel workbook. Lets say we have a starting table, tableA in the database. The excel macro keeps a record that userB has updated their Excel macro in the last 5 mins (for example), and if they have, it assumes its ok to overwrite the MySQL table with userB s version of the table. Then, they can update the main sheet/table to be pushed in Sheet mainfrom the extra data in SheetB. Then fetch the data from the server into a separate If there is, then warn userB that there is new data in the MySQL database which hasn't been updated in his When userB attempts to write their version of the table ( tableC) to the database using the macro, instead of blindly writing to the table, first check if there is any existing data in that row andĬolumn of the table in the MySQL database. Lets assume userA has already updated their tableB to the MySQL database.
These are 2 ways I can think of for overcoming the issue: Immediately update and notify userB when the data in the MySQL database is updated by userA. Research, I didn't see a obvious manner by which userBs Excel instance would Is enabled in a Excel workbook shared in OneDrive). That the database has been updated by userA (similar to how when co-authoring This is not intended behavior, as ideally userB would know This would lead to overwriting userAs data. He makes a change to the table (creates tableC) and writes to the same row andĬolumn of userA. At the same time, userB also has the same table open in Excel. userA makes a change to the table (creates tableB) and writes it to the MySQL database using the macro. Say userA and userB pull data the tableA from the MySQL database into Excel. Well, such as using using a direct connection to MySQL ( ) Things simple, I was just planning to write some VBA/Python code based onĬolumn based data from a specific sheet and dump it in the database. Trying to develop a prototype to demonstrate that the data can be stored on aĬentral server where multiple people can directly read and write from. I know that Excel provides ODBC drivers for most Databases. However because the data is stored on their own computers, it gets lost say The amount of numerical data is not too large (~10mb per person over a year), With time however, the Excel tables get pretty large. In my project users maintain data in Excel tables (with proper row and column
0 kommentar(er)
