Alternative drill down?

Hello all.

Lately I've been dealing with alot of corruption related problems with my
back end so I'm beginning to think of ways to try and improve the situation.
I had an idea that's alot like a drill down technique and I'd like to see
what others think about it, so here goes:

1. open main forms for read-only access

2. once a user finds a record to edit, user clicks an edit command button

3. open a recordset for that specific record using a query statement

4. use the getrows method to return an array of the data for that record

5. open a new form in single form view with no record source or control
sources and populate the form with data from the array

6. user modifies data and clicks an 'update' button

7. collect and process all data in the form into an update query statement,
then run.

8. main form is requeried.

The reason that I wanted to use arrays is to avoid consequences from a lost
connection. I'm hoping that when a user loses his or her connection when
it's read-only there will be less lock downs of the back end. So, am I out
of my mind or what? Does anyone have any suggestions?

hi,

JString wrote:
The reason that I wanted to use arrays is to avoid consequences from a lost
connection. I'm hoping that when a user loses his or her connection when
it's read-only there will be less lock downs of the back end. So, am I out
of my mind or what? Does anyone have any suggestions?
Nice ideas, but than why use Access?

Have you tracked down your corruption problems to a cause?
Sometimes corruption occurs when you have an instable network due to
defect switches or nics.

When you can't identify a cause there is only one thing I would try:
using a permanent open recordset.
This is basically a performance trick to reduce network traffic.
Normally the .ldb file for the backend is created and deleted again and
again.

If this doesn't work, I would consider using SQL Server (Express) as
backend...


mfG
-- stefan --

I've never heard of that method. How would I go about setting it up?

"Stefan Hoffmann" wrote:

hi,

JString wrote:
The reason that I wanted to use arrays is to avoid consequences from a lost
connection. I'm hoping that when a user loses his or her connection when
it's read-only there will be less lock downs of the back end. So, am I out
of my mind or what? Does anyone have any suggestions?
Nice ideas, but than why use Access?

Have you tracked down your corruption problems to a cause?
Sometimes corruption occurs when you have an instable network due to
defect switches or nics.

When you can't identify a cause there is only one thing I would try:
using a permanent open recordset.
This is basically a performance trick to reduce network traffic.
Normally the .ldb file for the backend is created and deleted again and
again.

If this doesn't work, I would consider using SQL Server (Express) as
backend...


mfG
-- stefan --

hi,

JString wrote:
I've never heard of that method. How would I go about setting it up?
using a permanent open recordset.
Create a new form with this code behind:

Option Compare Database
Option Explicit

Private m_Recordset As DAO.Recordset

Private Sub Form_Close()

m_Recordset.Close
Set m_Recordset = Nothing

End Sub

Private Sub Form_Load()

Set m_Recordset = CurrentDb.OpenRecordset("anyTable", dbOpenSnapshot)

End Sub

Open this form at your application start using

DoCmd.OpenForm FormName:="yourForm", _
WindowMode := acHidden


mfG
-- stefan --