I suppose that you must have some sort of problem in saving the subform when it's data have been modified. You may also have this kind of problem if you are using the RecordsetClone (or Recordset.Clone? I don't remember the difference between these two) method; especially if you are using ADP 2000 or 2002 instead of 2003.
Set the UniqueTable and ResyncCommand on both the main form and the subform and possibly that you will be fine. Using the SET NOCOUNT ON for all of your procedures is not a bad idea, too.
Take a look with the SQL-Server Profiler to get a better look at what's happening and, very important, set the error trapping to "Break on All Errors" to make that any error doesn't go into the silent mode.
Personnally, I never use filtering so I cannot tell you if their use can or cannot affect the read-only state of your main form.
-- Sylvain Lafontaine, ing. MVP - Technologies Virtual-PC E-mail: http://cerbermail.com/?QugbLEWINF
"kobi via AccessMonster.com" <u24890[ at ]uwe> wrote in message news:66afcb25aac9d[ at ]uwe...
[Quoted Text] >I have an adp project that includes a main form tied to a query that is > manipulated by a criteria string to filter records when opened. The > subform > is tied to the main form, the record source is the table to allow editing. > The problem is this.....when you open the form the buttons on the main > form > work fine. As soon as you edit anything in the subform, none of the > buttons > will work unless you close the whole form and requery the data. I suppose > if > I simply requeried the data to reset the main form's recordset that would > do > it, but they could have gotten to this form by means of 3 different forms > that filter and there's really no way to know what they filtered for. > Essentially I suppose, I'm looking for something that says, requery the > existing recordset but for the life of me, can't figure out the right > combo > to get this to work. Help? > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-adp-sqlserver/200609/1>
|