Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 355
  • Last Modified:

Advice on populating an unbound form

Hello,

I've developed two access form that use an underlying view from an sql server backend.  Basically, this view displays a pivoted view of the data.  The main form is a continuous form where each record is populated from the aforementioned view.  Each record has a detail button which when clicked, is used to display a detailed version of the record in single form view.  Everything is working fine.  However, management wants to be able to change data via the main form (in continuos view)  However since this data is aggregatted data, the only way I can think of to do this is to make this form an unbound form and to populate it via ado.  However, I don't think there is a way to assign data to an unbound continuous form.  I think that the only way to make changes to the data would be via making the detail form an unbound form and to populate that form which is in single form view via ado.  Are there any other alternatives?
0
chtullu135
Asked:
chtullu135
  • 2
1 Solution
 
Jeffrey CoachmanMIS LiasonCommented:
?
Care to simplify your question here?

Forget what you have already, ...(I think most experts were confused by your post)...

Perhaps it would be easier if you simply explained your ultimate Goal?

JeffCoachman
0
 
Nick67Commented:
It's lots of coding, either way.
But you could pull your view data down into local tables to make it editable, you then have to push changes in those local table back to the underlying tables involved.

On the SQL Server side you could conceivably create an INSTEAD OF trigger on the view so that it becomes updatable.  I've looked at those, but the documentation I've been able to Google up isn't great, and with production data, I don't want to test it.  But that may be a workable approach, although <<since this data is aggregatted data,>> may also be a fly in the ointment.

I use the 'temp' tables approach myself, and have written an article about it
http://www.experts-exchange.com/Microsoft/Development/MS_Access/A_6692-Overcoming-unbound-continuous-forms-limitations-by-staging-data.html
0
 
chtullu135Author Commented:
I went ahead and created two forms.  One is a read only form (continuous records) that is populated by an underlying query that displays all the underlying records in an abbreviated display (only a few fields are displayed".  When the user selects a record, and clicks view details, a the key field value is passed to a sproc on the server which returns only that record to the unbound etail form.  Any changes made to  that form will be used will update the underlying table on the server via a stored procedure.  I will be passing both the original values and the new values to the stored procedure.  The reason I will be sending the original records is to address  any concurrency issues that may arise.
0
 
chtullu135Author Commented:
The solution I came up with seemed to work bes
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now