You are asking a lot of questions that quite frankly, stray beyond the realm of peer to peer support. In a word, yes, it is feasible. There may be some business reason for maintaining the backward compatibility. If the access db's could be moved to MSDE, that would make the job easier. There are a lot of facts I surmise that would have to be known in order to adaquately answer this question and further, to make the proper reccomendations.

Please feel free to email me privately on this issue. Perhaps I could provide some services to your company with respect to this project...






>I'm taking over a project with a VB middle and an Access Backend. The client wants the DB upsized to SQL Server but wants the VB middle to be able to work against use either the existing Access backend or the new SQL Server backend. I admit I know little about this and it is past time I learn.
>
>Is this feasible? I don't see the need of maintaining the backward compatibility with Access but would like to know your opinion.
>
>What would you recommend to the client?
>
>There is lots of code like this:
>
>strSQL = "SELECT EMPLOYEE.*, FACILITY.*, COSTCENT.*, DIVISION.*, EMAIL.*, SupervisorLink.SupervisedCostCenterID, SupervisorLink.SupervisedCostCenterDescription, WEBSITEINFO.* "
>strSQL = strSQL & " FROM DIVISION, Facility, CostCent, Employee, Email, WEBSITEINFO, SupervisorLink "
>strSQL = strSQL & " WHERE Division.DIV_PK = Facility.FAC_FacilityDIVFK "
>strSQL = strSQL & " AND FACILITY.FAC_PK = Costcent.COS_FacilityFACFK"
>strSQL = strSQL & " AND COSTCENT.COS_PK = Employee.EMP_CostCenterCOSFK"
>strSQL = strSQL & " AND Email.EMA_PK = Facility.FAC_EmailEMAFK"
>strSQL = strSQL & " AND Facility.FAC_WebsiteInfoWEBFK = WebSiteInfo.WEB_PK"
>strSQL = strSQL & " AND SUPERVISORLINK.SupervisorID = EMPLOYEE.EMP_PK"
>strSQL = strSQL & " AND EMPLOYEE.EMP_LoginID = '" & strLoginID & "' "
>strSQL = strSQL & " AND EMPLOYEE.EMP_Active"
>strSQL = strSQL & " AND FACILITY.FAC_Active"
>RS.Open strSQL, DataConnectionString(), adOpenStatic
>
>EMPLOYEE.EMP_Active and FACILITY.FAC_Active are logical fields in access and this query fails against SQL server.
>
>How would you deal with this and other problems?