unbound continuous form 1

[jordanking]

Hello,

I am looking for suggestions on how to create an unbound continuous form. I use an access databse project that is connected to a SQL server 2005 back end.

I want to use an unbound form because:
-I can handle all errors and data integrity myself
-the form is complicated and reprsents data from many tables(meaning there is no table or query to which it can be easily bound).
-To reduce server traffic and record locking

From what I have found online, most people suggest to work with a temporary table, binding it to the form, and then executing stored procedures to move that data to the desired target tables.

I was just wondering if anyone had other suggestions before I dive into this.


.....
I'd rather be surfing

 

[PHV]

By definition (IMO) a continuous form is bound.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[dhookom]

The only alternative that I can think of is a value list listbox.

Duane MS Access MVP
Now help me support United Cerebral Palsy

 

[missinglinq]

It's amazing how these things go in cycles! I hadn't seen this scenario presented in six months or more and this is the third post I've seen on it today! Yes, the only really sane way to do this is to bind that data to a temp or holding table, do your thing, then when you're done, move all the records to your permanent table and either delete the records in the holding table or simply delete the table, if you're comfortable creating a temp table each time.

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[jordanking]

thanks for the posts,

I did not want to create temp tables for each user, felt like I had just been lazy in my DB design, let alone numerous other red flags about creating temp tables on the fly.

so after sleeping on it, what I did was create one unbound form that deals with one record at a time, but has a small uneditable subform on it that lists a few of the previous entries made by the user with a "button" to bring one of the subform records into the main form, this way I can force all my data integrity checks upon one current record before getting a previous one or entering a new record.

all in all it looks like and works a lot like a continuous form, so my client is happy, but it actually is unbound, which makes me happy.

if anyone wants to know more, just let me know


.....
I'd rather be surfing