Andreas, I have the same concern as you but am sure there's a simple explanation somewhere. If I have any kind of a hiccup the db seems to get in such a state that when I try to start a session with it in SQL Studio I get an error message: Unable to connect to data source; -708 SERVERDB System not available. This happens whether I reboot my server, or whatever I've figured out to do in my limited experience. I'm sure there's a way to recover from it (at least there had better be!) but right now that is far down my list of problems and will tackle it when I desperately need to.
Jon "Andreas Sander" <[EMAIL PROTECTED]> wrote in message at9tf4$i3l$[EMAIL PROTECTED]">news:at9tf4$i3l$[EMAIL PROTECTED]... > Hi Jon, > > your explanations where very interesting cause i am also converting an > application to SAPDB although it is neither Access nor uses it the DAO. > I have already toasted a database too when i tried to add more data to a > database than data would fit into the created database file. > > With your attempts we have three toasted database files. Now i ask me the > question, am i willing to accept this? > It is fully OK, if there is a failure in my program and no data is written > to the database or i get error messages. But may the database be toasted > because of this? What conditions else will toast the database? When i sell > my applications to dozens of customers, how many of them will get toasted > databases because of unknown conditions? > What do you think about that? > > Andreas _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
