Re: Best Pratice-Remore ADO Access

• Previous message: DDJ: "Re: Best Pratice-Remore ADO Access"
• In reply to: Saga: "Re: Best Pratice-Remore ADO Access"
• Messages sorted by: [ date ] [ thread ]

Date: Sun, 12 Dec 2004 20:03:54 -0700

> 2. For editting data, always have on hand the primary key
> for the record and use an UPDATE statement with a
> where clause to update a specific record (or specific
> group or records).
>
> 3. To add new data to the table, use an INSERT statement.

I responded incorrectly to "Wart"'s post...I will be using the UPDATE
statement.

>
> 4. For non trivial queries, use stored procedures.

I've been thinking about this. Our program ships with an Access db backend,
but users can upgrade to SQL. Can I, with code, create these stored
procedures on a user's SQL Server without going through a lot of brain
damage (I'm thinking about problems with permissions etc.).?

>
> 5. Whenever possible, make the serverwork, not the client
> (sort ot a rehash from the previous item).
>
> How is your WAN connected? Does it go over the
> Internet? I ask this becasue I am now doing research
> to see how I can build an architecture where the front
> end app will be installed on clients and the SQL Server
> will be in some remote site. I am hoping to be able to
> use the Internet to move data back and forth. Although
> I have done this kind of thing before, it has been limited
> to internally wired WANs, where each satellite office
> is connected by routers and it is all just a great big
> private network. To be able to do this through the
> Internet is another story. If you went that way, I certainly
> could use any advice that you might have, including the
> logic that you used to connect the clients with SQL Server.

We are assuming our users just have an Internet connection (slow or fast),
and we want to give them the option of switching our program to "remote"
mode, where we just process one record at a time, rather than the "normal"
processing, which looks to all records for the user. Without much
experience in these matters, YOUR experience would be helpful!

>
> Thanks!
> Saga
>
>
> "DDJ" <johnson@milehi.com> wrote in message
> news:0x5ud.32$td2.4639@news.uswest.net...
> > We are creating a form for our VB 6 app users to edit some add and edit
> some
> > data over a WAN connection to a SQL Server. What is the best method to
> set
> > up the ADO objects under these circumstances? Specifically:
> >
> > 1. I am assuming that the Connection object should only be opened when
> > reading or writing data, correct?
> >
> > 2. When writing data, I am assuming that using a Command object with an
> > INSERT clause would be the most efficient method, correct?
> >
> > 3. When reading the data from a record, I think I've read that the
> > recordset object creates a lot of overhead, so it's generally not the
best
> > way to do it. If true, then how do I retrieve the data?
> >
> > 4. Since the user will need to select a specific record when they want
to
> > edit the data, what is the best way to have them select the record they
> want
> > to edit, without unnecessarily retrieving too much data? Kind of an
open
> > ended question, I know. But if anyone can pass along any useful
> guidelines
> > to do this, I would appreciate it! Seems like you almost have to use
the
> > recordset object to do this, regardless of how many fields from the
record
> > you will be retrieving...
> >
> > Any feedback appreciated.
> >
> > Dan
> >
> >
>
>

• Previous message: DDJ: "Re: Best Pratice-Remore ADO Access"
• In reply to: Saga: "Re: Best Pratice-Remore ADO Access"
• Messages sorted by: [ date ] [ thread ]