Ok, come on. The new Access application can't possibly convert everything from my DataEase application, can it?

A. As long as you approach this with a reasonable expectation level, yes we do. By reasonable, we mean you're going to get an Access application that performs in a reasonably similar fashion to your DataEase application, but that is still an Access application.

In other words, we didn't rewrite DataEase in Visual Basic for Access. Items like record navigation, searching, filtering, etc. will now be serviced in the manner that Access does things, not the way DataEase does things. We also don't attempt to convert things like special characters (single-line and double line boxes on a screen layout, for example), printer control codes, external program calls, etc. Our formula derivation engine functions differently than DataEase', but, in most cases, the results are the same.

We don't handle 'Long:' fields the way DataEase does (but we'll convert them to memo fields for an additional fee, if you ask). Now if you come in expecting each and every function key to work exactly the same way ... more.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.