JasonEnsor
Programmer
Hi Guys,
I have been working on upgrading a system for some colleagues, all was going well except that now I am being told they need to allow multiple users to utilise the system at the same time.
I have prototyped a system that uses Excel with userforms. It allows the user to insert customer information and view it based on criteria i.e by date, customer surname etc. The reason I am using Excel is 1) The company doesn't support Access which would have been ideal as they need a database really. 2) Excel is where my strengths lie.
I am not a big fan of sharing workbooks, in the past it has caused the current users to lose data, and for the workbooks to become corrupted. The only way I can see around this is to use multiple workbooks and then merge the data in to the main workbook. The big concern I have here is ensuring that each row is assigned a Unique Id (wouldn't a database be just great for that). The reason for needing the Unique Id is that currently when the user searches for data I load the information on to a listview control, I use the Unique Id as a way of finding that row of data in the spreadsheet to allow the updating of the record.
To top it off I am due to leave my current position early Jan, so would ideally like to get this system built and tested, so I am looking for some ideas on how best to approach this.
I have considered using ADO to push and pull data from the main worksheet, or the use of csv files that are imported in to excel.
Does anyone have any ideas on a good approach at making this system work.
Each customer will have multiple rows of data, so the customer id can not be used as a unique id.
Many thanks in advance, I can happily clarify any information that is needed.
Regards
J.
I have been working on upgrading a system for some colleagues, all was going well except that now I am being told they need to allow multiple users to utilise the system at the same time.
I have prototyped a system that uses Excel with userforms. It allows the user to insert customer information and view it based on criteria i.e by date, customer surname etc. The reason I am using Excel is 1) The company doesn't support Access which would have been ideal as they need a database really. 2) Excel is where my strengths lie.
I am not a big fan of sharing workbooks, in the past it has caused the current users to lose data, and for the workbooks to become corrupted. The only way I can see around this is to use multiple workbooks and then merge the data in to the main workbook. The big concern I have here is ensuring that each row is assigned a Unique Id (wouldn't a database be just great for that). The reason for needing the Unique Id is that currently when the user searches for data I load the information on to a listview control, I use the Unique Id as a way of finding that row of data in the spreadsheet to allow the updating of the record.
To top it off I am due to leave my current position early Jan, so would ideally like to get this system built and tested, so I am looking for some ideas on how best to approach this.
I have considered using ADO to push and pull data from the main worksheet, or the use of csv files that are imported in to excel.
Does anyone have any ideas on a good approach at making this system work.
Each customer will have multiple rows of data, so the customer id can not be used as a unique id.
Many thanks in advance, I can happily clarify any information that is needed.
Regards
J.