I have just about finished an application for requisitioning construction contracts. Most of the bugs have been handled but I can't seem to figure out what to do about "empty table data".
When I program I input bogus data to work with for testing and debugging. The problem I have is when I empty all the tables, before packaging and deploying, so that my user can have a clean data base, the application crashes as the pages load. My feeling is that this happens because the tables are empty. If I go to the Visual Data Manager and install data in each table, the program runs as designed.
This may be helped with location and or instances of the "Refresh" methods I have used. Pretty much all the ADO controls for my program require changing the "RecordSource" via code and user input.
Has this been a problem for anyone else? Any suggestions on this will be greatly appreciated.
Thanks,
Dwight
When I program I input bogus data to work with for testing and debugging. The problem I have is when I empty all the tables, before packaging and deploying, so that my user can have a clean data base, the application crashes as the pages load. My feeling is that this happens because the tables are empty. If I go to the Visual Data Manager and install data in each table, the program runs as designed.
This may be helped with location and or instances of the "Refresh" methods I have used. Pretty much all the ADO controls for my program require changing the "RecordSource" via code and user input.
Has this been a problem for anyone else? Any suggestions on this will be greatly appreciated.
Thanks,
Dwight