Moving to SQL Server

i think this is how i already built my FE, everything is filtered according to what the user needs to work on
Not sure if you have understood what Pat was saying or whether it is your termininology. Filtering occurs in forms after you have brought across the recordset. Pat is saying apply criteria before you bring across the recordset.

Note if you use the WHERE parameter for docmd.openform, this is actually a filter.

So instead of using the openform where parameter or in code something like

me.filter="CustID=" & 123

you build it into the recordsource

me.recordsource ="SELECT * FROM myTable WHERE " & "CustID=" & 123
 
One thing I have learned from transitioning to sql be, is that you realise access is very quick and easy to work with. It will make you consider going back to access....

If you want to change or modify your back end when its in sql, prepare for pain.

Things that access just does automatically, dont happen automatically. For example, primary IDs, being able to just do anything to any table, this is something that has to be "allowed". Datatypes are not immediately all recognisable or sensible (in my opinion).

As for your front end, most will be fine, but you may notice some vba needs to be modified. In my case its mainly due to the fact that with access as soon as some data is created for a record, the record is created, in sql, its not. A few dlookups had to be modified, some procedures needed to be rethought through.
 

Users who are viewing this thread

Back
Top Bottom