I have been developing MS Access applications for my clients and subscribing to EE for over 15 years. EE has been an invaluable resource working thru many projects.
In my Access applications I always split the procedures from the data. Up to this point all of the data backends have been MS Access.
I am using Access 2013 to develop my first app that will have a SQL Server backend. I have many SQL tables defined and I have developed many logic routines converting data from the old legacy format to the new SQL tables. Currently most of my SQL tables are linked to the Access front end using the Linked Table manager.
I have some questions as I think about moving toward production
Connecting to Data:
In my prior Access apps I have a routine that will automatically link the backend Access tables based on a .ini parm read at startup. Each system has it's own ini. This way the app adapts to each operating environment without having to manually link the tables.
SQL tables can also be linked to an Access front end using the Linked table manager. Is there a routine that will automatically relink SQL table based on an .ini parm just like my current routine does for linked Access tables?
Bound or Unbound Forms?
Using SQL tables linked thru the Linked Table Manager, it is possible to create forms bound directly to a SQL table, just like you can do with Access tables. Is something that is recommended? Or, is it better not to bind forms to tables in SQL server? What are the pro's and cons of either approach?
I will be using Views extensively. I have heard and read differing opinions on using stored procedures. Some say there in no great benefit, other say they should be used extensively. I came upon one response to a SQL question stating that every create, read, update and delete (CRUD) of a record should be done using stored procedures. What is your experience?
As instructed/read I have included a field defined as 'TimeStamp' on all of my record definitions. My understanding is that SQL will use this field to determine what to do in record locking situations. I don't use this field for anything in the app. Do I need to load a value in the field or does SQL handle it on its own.
I installed SQL 2014 Developer accepting the standard set up options. Are there any setup options or values that should be set?
If there is any other insight into this process you can offer I would appreciate it.
I realize this is not a specific directed question with a correct answer but I am looking for feedback from developers that have been thru this process. I will award points to all helpful contributions.