Bookmark this on Delicious
Recommend to StumbleUpon
Don't let me put you off Base... it has worked well for me for many years. Just recently I had a very unusual incident which I am putting here, just in case you encounter something similar.
I had a slightly large, but very simple table. From that, with the wizard, I created a simple form. All fields, just default settings.
The one bit of "fancy" was that many of the fields were of type "Text (fix) [char]".
I thought that the form was working... but when I came to it in a new session, I was getting 0s where I would have expected things like "f12c16a" (don't ask!).
Proceeding carefully, I thought, I tried to fix... and ended up making the whole .odb file useless. If you find yourself with the 0's problem proceed VERY carefully, backing up your .odb file frequently!
Editing the form, I found that the errant columns were for some reason of type TextBox. Using "replace with" FormattedText on the columns seemed to fix things... form displayed properly. But then came the crash, and disaster. Sigh. Very disappointing... but one disappointment in several years of work. And a reminder to back up more often. And a vindication of my obsessive use of data entry forms.
There was a benefit arising from this unhappy experience: It pushed me to look again at using a MySQL server to host my data, continuing with Open Office, but merely as the front end client.
Click here to visit editor's Sheepdog Software (tm) freeware, shareware pages.
Page tested for compliance with INDUSTRY (not MS-only) standards, using the free, publicly accessible validator at validator.w3.orgMostly passes. There were two "unknown attributes" in Google+ button code. Sigh.
. . . . . . . P a g e . . . E n d s . . . . .