bound form data entry = yes network traffic

[gt]

Hi -

I know that on a bound form setting the data entry property to yes prevents
the form from displaying any records. I'm assuming this means no records are
transferred over the WAN. Is that correct?

In an effort to reduce network traffic, many of my colleagues use unbound
forms and vba/sql to insert the data entered into the form to an Access
back-end table (split database). But in so doing they lose the benefits of
bound forms.

If I can simply set a bound form's data entry property to Yes and accomplish
the same goal (minimize network traffic), I would prefer to do that.

Recommendations?

Thanks in advance
gareth

[Jeff Boyce]

Gareth

Access over a WAN is a troublesome proposition. Albert Kallal offers a
description of the issues (try an on-line search).

Regards

Jeff Boyce
Microsoft Office/Access MVP

"gt" <g...@discussions.microsoft.com> wrote in message
news:C74319A3-8B33-48D8...@microsoft.com...

[Beetle]

I don't believe that's correct. The Data Entry property of the
form only determines what is *displayed*, not what is in the
record set.

You should use a query as the record source of the form. You
can use criteria in the query to limit the record set to whatever
you want. If you don't want to pull any existing records, use
criteria of Is Null in the PK field, or something like that.

You are correct that your colleagues are losing one of the
greatest benefits of Access (bound forms). I would question
why they are using Access as a front end at all if they are
not going to use bound forms. There are probably other
programs that are better suited to the unbound approach.

--
_________

Sean Bailey

[Beetle]

Actually, Jeff is right. I didn't catch that you said WAN in
your post the first time I read it. Access is not well suited
for use over a WAN.

--
_________

Sean Bailey

[gt]

Thanks for both your responses Sean.

I know Access is not well-suited for a WAN - even though the db is split
into front and back. I think to keep our IT folks happy, I'll use an unbound
form and write one record at a time using a sql insert query in vba.

[gt]

I'll google that - and thanks for yr. response Jeff.

[Jeff Boyce]

If I recall correctly, you have another option via terminal emulation,
Citrix, etc.

Regards

Jeff Boyce
Microsoft Office/Access MVP

"gt" <g...@discussions.microsoft.com> wrote in message

news:27E229BF-A2F3-4DFD...@microsoft.com...

[Albert D. Kallal]

> I know that on a bound form setting the data entry property to yes
> prevents
> the form from displaying any records. I'm assuming this means no records
> are
> transferred over the WAN. Is that correct?

You can also open the form in add-mode. Eg:

DoCmd.OpenForm "Contacts", acNormal, , , acFormAdd

So, for the most part, yes you are correct.

>
> In an effort to reduce network traffic, many of my colleagues use unbound
> forms and vba/sql to insert the data entered into the form to an Access
> back-end table (split database). But in so doing they lose the benefits of
> bound forms.

Yes, and often this approach will save you any bandwidth.

lets see:

create query....open table...load data. (network traffic)

write bunch of code to fill up un-bound form

now, to save:
create query, open table ...write data.... (whole bunch more network
traffic). If one is not carful, all that code to open up and pull the data
will cause additional overhead then simply having the form bound in the
first place (you not be opening + closing the table).

All that opening and creating of queries can often wind up causing MORE
traffic then just using bound form. The trick here is ALWAYS open the form
to the ONE record you need. so, simply "ask" the user for the one record
first. I explain this concept here:

http://www.members.shaw.ca/AlbertKallal/Search/index.html

You might consider other solutions for wan...I explain the problems and
solutions here:
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOO...@msn.com