I have a "New Call" form that works just fine in the original Access Application but now that it has been converted to an ADP (Access Project) I cannot find a way to get the form to start on a new record.
I have tried
Private Sub Form_Load()
DoCmd.GoToRecord , , acNewRec
'Startnewcall_Click
End Sub
which errors out with "You can't go to the specified record."
and setting the "Data Entry" property on the form to "yes" causes the form to come up blank. In blank I mean nothing is visible on the form not even the field names much less where to enter the new record data.
Just so you know here is some background on this project.
There are 3 tables plus the Swtchboard that have been migrated/moved over to the SQL server. I have performed this to both SQL Server 2000 and 2005 for test purposes.
The version of access is 2003 so the migration works best with the SQL2k server. Well at least the Designer works anyway.
I spent about 2 weeks cleaning up table names and column names then going through the forms, reports, quearies, and VBA code to eliminate obvious problem areas before attempting to "upsize" the Access Application.
Because of problems with some of the Date and Time fields in the [Activity] table I have found it easiest to migrate that data through SSIS.
Getting the Add New Call form working I hope is the last stumbling block needed before letting the department test the "Upgraded" version.
Any help would be GREATLY appreciated!!!!!!!!!!!!!!!!!!
Thanks
John Fuhrman
faq329-6766
thread329-1334328
thread329-1424438
I have tried
Private Sub Form_Load()
DoCmd.GoToRecord , , acNewRec
'Startnewcall_Click
End Sub
which errors out with "You can't go to the specified record."
and setting the "Data Entry" property on the form to "yes" causes the form to come up blank. In blank I mean nothing is visible on the form not even the field names much less where to enter the new record data.
Just so you know here is some background on this project.
There are 3 tables plus the Swtchboard that have been migrated/moved over to the SQL server. I have performed this to both SQL Server 2000 and 2005 for test purposes.
The version of access is 2003 so the migration works best with the SQL2k server. Well at least the Designer works anyway.
I spent about 2 weeks cleaning up table names and column names then going through the forms, reports, quearies, and VBA code to eliminate obvious problem areas before attempting to "upsize" the Access Application.
Because of problems with some of the Date and Time fields in the [Activity] table I have found it easiest to migrate that data through SSIS.
Getting the Add New Call form working I hope is the last stumbling block needed before letting the department test the "Upgraded" version.
Any help would be GREATLY appreciated!!!!!!!!!!!!!!!!!!
Thanks
John Fuhrman
faq329-6766
thread329-1334328
thread329-1424438