Dear Forum experts, I require a little advice to hopefully get me started in the right direction.
A little background first...
In a previous employment I administrated a large database created using MS Access and a huge amount of VBA. The database was split in two, a front-end stored locally on each of the Windows PC's (multiple users) for entering and viewing data using Forms, and a back-end which was stored on the company network that held all of the data in Tables. The database was used to store machine information, maintenance schedules and inspection reports along with all manner of other data and productivity information. Reports would be automatically issued detailing what maintenance was required on which machines and graphs to show how productive the machines were and thus how effective the maintenance was. I even did some work with pivot tables/charts so that the data could be drilled into enabling the various production managers to better understand where resources were required.
My new requirement...
Having shown some of the reports produced from the old system to my current employer, they are very interested in implementing something similar. I would like to modernise it and use B4A so that all information can be entered and made available using handheld tablets. I realise that pivot tables/charts might be out of the question at the moment but so long as the data is available in a networked database then there is no reason why I couldn't implement something else for this. The data will still be stored on a Windows PC which I suspect is running Windows Server Edition. I could also continue to use MS Access on some of the shop-floor PC's although this might complicate things? Maybe implementing a B4J equivalent of the tablet B4A code would be better?
My questions...
1). What would be the most suitable way to store the back-end data?
2). Is RDC still the best method of connecting to the back-end data?
3). How do I handle multiple users and concurrent data (MS Access did this automatically for me)?
4). What is the best way to handle the front-end accessing and updating data?
5). What tools and utilities are there to make life easier? I've done a lot of SQL but would still consider myself as somewhat of a beginner. MS Access has a utility that allows me to create queries etc and I then copy and manipulate the SQL statements to my exact needs.
6). Security considerations? It would be nice that at a later stage I could allow remote access from outside of the LAN, allowing production data to be viewed from anywhere.
How much of this is possible? I suspect that it all can be done although I might not be the right man for the job, which I've already pointed out to them? I've no PHP Scripting experience and JSON is also a new term that I am not familiar with. Where to start? Advice please?
Thanks,
RandomCoder
A little background first...
In a previous employment I administrated a large database created using MS Access and a huge amount of VBA. The database was split in two, a front-end stored locally on each of the Windows PC's (multiple users) for entering and viewing data using Forms, and a back-end which was stored on the company network that held all of the data in Tables. The database was used to store machine information, maintenance schedules and inspection reports along with all manner of other data and productivity information. Reports would be automatically issued detailing what maintenance was required on which machines and graphs to show how productive the machines were and thus how effective the maintenance was. I even did some work with pivot tables/charts so that the data could be drilled into enabling the various production managers to better understand where resources were required.
My new requirement...
Having shown some of the reports produced from the old system to my current employer, they are very interested in implementing something similar. I would like to modernise it and use B4A so that all information can be entered and made available using handheld tablets. I realise that pivot tables/charts might be out of the question at the moment but so long as the data is available in a networked database then there is no reason why I couldn't implement something else for this. The data will still be stored on a Windows PC which I suspect is running Windows Server Edition. I could also continue to use MS Access on some of the shop-floor PC's although this might complicate things? Maybe implementing a B4J equivalent of the tablet B4A code would be better?
My questions...
1). What would be the most suitable way to store the back-end data?
2). Is RDC still the best method of connecting to the back-end data?
3). How do I handle multiple users and concurrent data (MS Access did this automatically for me)?
4). What is the best way to handle the front-end accessing and updating data?
5). What tools and utilities are there to make life easier? I've done a lot of SQL but would still consider myself as somewhat of a beginner. MS Access has a utility that allows me to create queries etc and I then copy and manipulate the SQL statements to my exact needs.
6). Security considerations? It would be nice that at a later stage I could allow remote access from outside of the LAN, allowing production data to be viewed from anywhere.
How much of this is possible? I suspect that it all can be done although I might not be the right man for the job, which I've already pointed out to them? I've no PHP Scripting experience and JSON is also a new term that I am not familiar with. Where to start? Advice please?
RDC - Simple way to create your own back-end database (Dated August 2013)
Access any database or system with B4AServer (Dated June 2011) I don't think this is applicable for my requirements.
Read/Write from/to a database on your harddrive (Dated July 2012) Is this still the best way?
RDC (Remote Database Connector) and Access mdb database (Dated September 2013)
Best approach for database in App (Dated January 2014) Is this still current and upto date?
Access any database or system with B4AServer (Dated June 2011) I don't think this is applicable for my requirements.
Read/Write from/to a database on your harddrive (Dated July 2012) Is this still the best way?
RDC (Remote Database Connector) and Access mdb database (Dated September 2013)
Best approach for database in App (Dated January 2014) Is this still current and upto date?
Thanks,
RandomCoder
Last edited: