July 27, 2015 at 4:07 am
I currently use access as FE to my sql db. My bog standard data entry edits/inserts etc are handled by bound access forms.
To move away from an access front end - do I need to write insert/edit procs for non bound forms - ie web pages?
Or would a new FE be a better place to handle the "binding" of data for user insert/edits?
Thanks, any links greatly appreciated.
July 27, 2015 at 7:37 am
Adam Sandler (7/27/2015)
I currently use access as FE to my sql db. My bog standard data entry edits/inserts etc are handled by bound access forms.To move away from an access front end - do I need to write insert/edit procs for non bound forms - ie web pages?
Or would a new FE be a better place to handle the "binding" of data for user insert/edits?
Thanks, any links greatly appreciated.
The topic you are asking about is a big one. I applaud you in wanting to get away from Access but you haven't really provided any details about what you want to do.
IMHO you would better off with a new front end AND procs for all of your data manipulation. This way you can easily generate a multi-layered application so the front end isn't doing the data work.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply