[AccessD] Anyone used dbSync?

Fred Hooper fahooper at gmail.com
Mon Nov 2 13:26:54 CST 2015


Hi Dan,

I was local and hard-wired to their network, using one of their PC's.

I've started on your 2) and have it working for the most-used form. Next
I'll extend it to the second most used to complete a proof of concept.
I've got working code that switches between the Access BE, SQL Server
BE, and ADO recordsets, so we'll assess the speed with all of the
alternatives using the same code, as much as possible.

Part of the reason I want to use recordsets is that their product is
mostly written in VB.Net. I expect that they will start a back burner
project to convert the Access FE and the recordsets should help some of
that.

I hadn't considered WinForms. Currently, they have all their people in
three adjacent rooms. Since one person has a 1.5 hour commute each way,
they might be interested in being able to work remotely. I'll talk to
them about it after I've done some reading. Thanks additionally for that
idea.

I've got a little Demo mdb that I used to debug the ADO recordset
approach if you or anyone else is interested.

Best,
Fred
> Dan Waters <mailto:df.waters at outlook.com>
> Monday, November 02, 2015 2:09 PM
> Hi Fred,
>
> Are you logged onto their network using a VPN and Remote Desktop from
> outside that network?  If so, your massive increase in speed is expected.
> ODBC table links connected to a SQL Server database from outside the network
> will never have acceptable speed.  No table link, Access or ODBC, ever has
> acceptable performance using a VPN on the internet.  
>
> If the application will only be actually used within the network, then just
> do the testing on identical tables on your PC.  When you're done just ship
> the FE to your brother in law and let him know he'll need to relink the ODBC
> table links to SQL Server on his server.
>
> If that doesn't work there are three other paths:
>
> 1) if possible, log into their network and do all the work on their server.
> 2) You could rewrite all the FE code using ADO.  This does not require table
> links and does provide good performance.  About 10 years ago I started to
> learn this but I no longer remember
> 3) Download Visual Studio Community 2015 (free) and learn to write a
> WinForms app.  Develop on your PC using SQL Server Express (or SQL Server
> Developer).  Very similar look and feel, great performance, and has the same
> purpose as an Access app.
>
> Short term 1 is best, 2 is OK.  Long term 3 is best.  2 used to be called an
> Access Project but today, learning Visual Studio is a better path long term.
>
> Still, unless you are going to keep tables in an Access .mdb file and in
> identical tables in SQL Server synchronized continuously, I don't believe
> that dbSync would be helpful.
>
> Good Luck!
> Dan
>


More information about the AccessD mailing list