Re: [DUG]: Can D5 Pro handle it?

[Nello Sestini]

Is there any reason that Paradox would not continue to handle things? Is there any reason that the existing application architecture would not work? or would I need to convert to Client/Server? I believe that the client has Winframe - but would there be any advantages to using Asta to provide Internet based access to the database? my experience with paradox on a LAN is that even an application with tight error handling and start/commit bracketed transactions can have db integrity problems if the lights go out on one of the machines in the middle of a transaction.   the reason (as best I understand it) has to do with problems flushing cached buffers of key blocks and table headers and internal stuff like that.   distributing the sessions over less reliable WAN connections as you describe increases the chances that this kind of disruption occurs - and exposes you to much higher risk of db crashes than you are used to.   Frankly, the thought of doing something like this with paradox gives me chills.    There is Interbase after all.   But if switching to IB isn't an option, I think you should test your app by doing things like starting a transaction and then unplugging the lan cable in the middle of it to see how fault tolerant your application is.   Transactions that need to do lots of complicated inserts while the database is in an inconsistent state are likely trouble spots.   -ns