Re: Using Visual Basic Net as front end - Access as back end

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



You have several good choices. If you are using .NET, use it with ADO.NET
and IIS and access the database with a web server. The method I prefer is to
use a Terminal Server and an Access front-end, because even very expensive
hardware on a sophisticated application will cost less than building the
application with a non-Access front-end. Since it typically takes 3 to 6
times as long to build a database application in VB or in .NET than in
Access. A really good Server with both Hardware and software will cost less
than $6,000. So consider the ROI, when making decisions.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

"CAM" <alex_martinez@xxxxxxxxxxx> wrote in message
news:eDa7$%23vvGHA.2436@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am wondering if someone has come across this before. Currently I am
using Access 2002 I developed an inventory tracking database, which this
database is used in California and in Florida. Both Inventory centers
(California/Florida) have their own database spited (Front-end - queries,
forms, macros, etc. and back end - tables only) in their respective state.
I originally wanted to have the backend located in the California
inventory center, which both California and Florida have access to.
Unfortunately, I could not have just one backend database it took Florida
about 40 to 50 seconds or longer to open up a form and about 2 minutes or
more to open up a report, which the backend was in California. Now I have
the California inventory center front end and the backend and Florida has
their own front-end and backend all this is due to slow performance over
our WAN across the country. About 5 years ago I developed a database
using Visual Basic 6 as the front end and Crystal Report as the report
writer and Access (tables and queries) as the backend. It worked great
and fast, but this database was used only in one location in our WAN not
over the other side of the United States. My thoughts are using Visual
Basic Net as the front end, Crystal Reports as the Report Writer and
Access as the backend (tables, queries). I would like to use this
combination by having the backend in California (Access), which both
California and Florida have access to. I want to try to retain saving all
of my tables and queries in Access if possible. Will this work? Can
Florida access the database without any major delays or corruptation
problems. Of course each users PC's will retain their own Visual Basic
net Front end to speed up the database. Their will be about 25 users per
inventory center. Or should I get Microsoft Sql server and use Visual
Basic Net. We are on a budget like most IT shops and I thought using the
combination of Visual Basic net, Crystal Reports, Access will be the least
expensive way to go. Can someone give me their input. I like to have
much input as I can get before I can do any major undertaking. Thank you
in advance.



.



Relevant Pages

  • Re: Using Visual Basic Net as front end - Access as back end
    ... database is used in California and in Florida. ... I originally wanted to have the backend located in the California ... I could not have just one backend database it took Florida ... more to open up a report, which the backend was in California. ...
    (microsoft.public.access.formscoding)
  • Re: Using Visual Basic Net as front end - Access as back end
    ... database is used in California and in Florida. ... I originally wanted to have the backend located in the California ... I could not have just one backend database it took Florida ... Report as the report writer and Access as the ...
    (microsoft.public.access.formscoding)
  • Re: Using Visual Basic Net as front end - Access as back end
    ... this database is used in California and in Florida. ... I could not have just one backend database it ... Crystal Report as the report writer and Access as ...
    (microsoft.public.access.formscoding)
  • RE: 5 access 2000 users and 1 AccessXP user
    ... I, too, have a split database with the backend on a server. ... > This is then followed by a message to the effect that the mde is corrupted. ...
    (microsoft.public.access.conversion)
  • Re: Access 2000 with SQL Server - MultiUsers
    ... However the drawback is more active connections to the server, ... As far as the backend goes I've run 50 to 200 people updating a MS Access 97 ... then disconnect from the backend. ... Jet doesn't disconnect you from the database ...
    (microsoft.public.access.externaldata)