L
Lee
I have an access application that's been upsized so that
all the tables have been moved to SQL Server. That itself
doesn't seem to be a problem. I started getting Access
crashes after I moved some of the controls on the main
form to a new tab on the main form. Whenever I make a
change to one of the fields on the new tab, if I just
navigate to a new record, the update occurs w/o error.
However, if the user presses the "Save" button, Access
Crashes without fail. The code behind the save button
just basically does a Forms!FrmMain.Form.Refresh which
hasn't changed. I can make any other changes and it
doesn't crash as long as I don't change any of the data on
the new tab. I've tried putting a breakpoint to see where
the crash is occurring. It seems to be right after
the .Refresh statment but before any other statement after
the .Refresh. Any help would be appreciated.
all the tables have been moved to SQL Server. That itself
doesn't seem to be a problem. I started getting Access
crashes after I moved some of the controls on the main
form to a new tab on the main form. Whenever I make a
change to one of the fields on the new tab, if I just
navigate to a new record, the update occurs w/o error.
However, if the user presses the "Save" button, Access
Crashes without fail. The code behind the save button
just basically does a Forms!FrmMain.Form.Refresh which
hasn't changed. I can make any other changes and it
doesn't crash as long as I don't change any of the data on
the new tab. I've tried putting a breakpoint to see where
the crash is occurring. It seems to be right after
the .Refresh statment but before any other statement after
the .Refresh. Any help would be appreciated.