Hey guys and gals, I am new to Alpha and fairly new to databases (after 6 years of MS Access I still know nothing!)
I am building a database for customers, invoices and employee time logging. Our users will manage the data almost 100% of the time from a mobile device, and at least for now, we will create the application as a web project. I have dabbled around a bit with Alpha for about a week now, and realized I really didn't know much about how the connection strings work. I already ordered hosting with ZebraHost, and we already have Office365, complete with a working (word is used loosely) SharePoint.
Now with the background out of the way, could you please tell me the pros and cons of:
A) External: Creating SQL tables and connection strings through Alpha (Tools>Create SQL Table...) that reside on a SharePoint
B) Native: I don't know much about this yet but I am guessing the tables would reside on the ZebraHost server within the Alpha files?)
Some of the functionality I need that may limit this would be tables that can be backed up easily, an application that can be updated (I'm talking about front end code stuff, not modifying table structure) but can still retain data that may have been added or changed while the update was being developed, and the ability to initially import data from our existing MS Access 2013 desktop database (or from one of the export options available for Access).
Again, I am new to this. Any and all info will definitely be appreciated, so if you need to school me or offer an alternative to how I am looking at this, I am all ears.
I am building a database for customers, invoices and employee time logging. Our users will manage the data almost 100% of the time from a mobile device, and at least for now, we will create the application as a web project. I have dabbled around a bit with Alpha for about a week now, and realized I really didn't know much about how the connection strings work. I already ordered hosting with ZebraHost, and we already have Office365, complete with a working (word is used loosely) SharePoint.
Now with the background out of the way, could you please tell me the pros and cons of:
A) External: Creating SQL tables and connection strings through Alpha (Tools>Create SQL Table...) that reside on a SharePoint
B) Native: I don't know much about this yet but I am guessing the tables would reside on the ZebraHost server within the Alpha files?)
Some of the functionality I need that may limit this would be tables that can be backed up easily, an application that can be updated (I'm talking about front end code stuff, not modifying table structure) but can still retain data that may have been added or changed while the update was being developed, and the ability to initially import data from our existing MS Access 2013 desktop database (or from one of the export options available for Access).
Again, I am new to this. Any and all info will definitely be appreciated, so if you need to school me or offer an alternative to how I am looking at this, I am all ears.
Comment