Installing AdabaseD for SO5.2 on Windows ME (2000?)
Lee Brown
I purchased SO5.2 when it first came out 3 yrs ago, but waiting until I had a better PC before installation. So far, SO5.2 works fine. However, I'm having a problem with properly installing AdabaseD.
I've installed it twice. First time I discovered my own error; I had a space in the path (C:\Program Files\AdabaseD). After reviewing some installation instructions, I learned that you can't have a space ANYWHERE in the path name. So, I moved my "AdabaseD" folder directly to my "C:\" drive, and edited my autoexec.bat file accordingly to read, "C:\AdabaseD". To be sure things would work fine, I re-installed AdabaseD, conducted a repair to SO5.2, restarted the computer and double-checked the environment settings in my autoexec.bat file which reads as follows:
DBROOT=C:\AdabaseD
DBWORK=C:\AdabaseD\sql
DBCONFIG=C:\AdabaseD\sql PATH=C:\WINDOWS; C:\WINDOWS\bin;C:\AdabaseD\pgm
Funny thing is, when I use the "echo" command at the DOS prompt for each setting, I don't receive what I think should be a proper reply telling me exactly where my AdabaseD has been installed as indicated above. Also, I'm receiving an error message that reads something like the following (Note: I'm posting this from work and not from my home computer where SO5.2/AdabaseD are installed): "Client unable to establish connection;-813 SERVERDB MUST BE RESTARTED".
My questions, therefore, are as follows:
1. Initially, I installed SO5.2 & AdabaseD for a single-user. Since my operating system is Windows ME (Millenium Edition, which I believe is commonly referred to as Win 2000), should I re-install SO5.2 under the network settings then configure for multi-user or leave everything as is?
2. Does the above error message mean AdabaseD is improperly installed or does it mean my computer can't find the exact location of the database file under AdabaseD? (Mind you, the name I gave my "test" database was "Financial Planner," and it did appear in the hierachical view of the Explorer.)
3. Per the SO5.2 User's Manual and the Companion, one can create an empty database using either dBase or AdabaseD. When using AdabaseD, is the "data source" the name of the database itself (i.e., "Address Book") or the name of the database object (e.g., table, report, query, etc.)?
4. When creating a new AdabaseD database, are the following steps correct: a) enter the data source, b) click the "New Data Source" button then follow the appropriate instructions, c) enter Administrator user name & password, or did I miss something? The instructions weren't that clear. (Either that or I'm just not grasping how to create a new AdabaseD database from scratch!)
5. On the AdabaseD tab, there are areas on the dialog box that indicate the location (and something else, but I can't remember what that is at the moment) where the database should reside on one's computer. Should that "residence" be the same as my %DBROOT path?
So many questions, so little time...
Can someone please provide guidance? I want to create a sample database (obviously) using AdabaseD, but creating one from scratch is a bit confusing.
Thanks for your support!
Nils Homp - Sun StarNews Support
Ill just get straight to the issue here.
The error message you receive occurs if you try to access an Adabas D database which has not been
started. Normally, an Adabas database will be started automatically when you access it
with StarOffice for the first time. For this to happen, however, it is necessary that the Control user has been entered.
The error message may also appear if the database server cannot automatically
be started. That would indicate some problem with your system configuration.
Now, the settings you posted seem to be just fine, except for one - the environment variable PATH must contain the following path:
%DBROOT%\bin and %DBROOT%\pgm (in your case, "c:\AdabaseD\bin" and "c:\AdabaseD\pgm", not "C:\WINDOWS\bin" and "C:\AdabaseD\pgm")
If you look carefully, you'll see the mistake - you have entered c:\windows\bin instead of c:\adabas\bin - this is the directory containing all the Adabas binaries so if the correct path is not entered, the program can't ever start.
Please change this and you should be set - if not, just get back to us right away.
Nils Homp
Sun StarNews Support
--
All responses posted to this newsgroup are provided without guarantees as to the suitability of their use. Although we believe the solutions or explanations given to be accurate and correct, we cannot guarantee the accuracy of the information contained.
Please do not reply directly to this e-mail address if you wish to continue further dicussion of this matter, as you will only receive an automatic response from our system. Instead, please reply to the message itself so further assistance can be provided via the newsgroup. Alternatively, you are welcome to have a look at our website for further information regarding our support services, which is available at http://www.sun.com/star/support
Lee Brown
It turns out my AdabaseD problems went much deeper than I thought. To fix them, I had to re-install the entire office suite (which was mostly due to my lack of understanding of how the program works). The re-install took some doing! Nonetheless, I have it working now. Thanks!
I'd like to share with readers some things I've learned that may help clarify some issues about AdabaseD and make working with the database program easier, particularly for first time users like myself:
1) SO/Adabase Glitches. If you're having problems getting AdabaseD (ver. 11) to work, or SO5.2 for that matter, download the SO5.2 patch at: http://www.sun.com/supportraining
Follow the links (keywords: StarOffice Patches, Patches) then click on the link for your operating system. For Windows users: I highly recommend using the FTP download link. Be advised that the download can take upwards of 2 hrs with a 56k modem. So, it's probably a good idea to do this overnight. Once the patch has been downloaded, follow the instructions at the bottom of the text file very carefully as you will need to copy several files over into your root or subfolder where your Adabase program files are located. Again, be VERY careful to ensure you COPY ALL THE FILES over, DO NOT MOVE THE FOLDERS over as Windows will not prompt you that you are creating a duplicate folder on your system. Be sure to re-start your computer after you've copied all the files from the patch, and save the original patch file to a separate disk or CD in case you need a backup later.
2) Keep Your Program Files in Order. Be sure to check your autoexec.bat files as outline in the above post. If the paths are wrong, your AdabaseD won't work correctly, if at all. If you must, run setup again and use the "Repair" feature, then re-start your computer.
3) Naming A Data Source. I was VERY confused as to exactly what a "data source" was (as I'm sure most who are more familiar with Access are) until I read between the lines. I now understand that a data source is merely a reference point YOU tell Adabase to use as the basis for your database. The data source can be (almost) anything - a spreadsheet, a text file, another database table, or in the case of a new database, any filename you tell Adabase to reference back to for pertainant information concerning your database. Example:
Database Name: Financial Planner
Database Type: AdabaseD
Data Source: Money
In this case, the filename "Money" is the reference file Adabase will use to plug all information concerning the overall structure of the "Financial Planner" database.
4) If you're like most of us, you're using Star Office/AdabaseD on your personal computer at home or in the small office. The SO5.2 Companion manual recommends installing SO/Adabase for use either as a "single-user, network server, or workstation". Furthermore, it recommends for single users to install AdabaseD using the "workstation" setup instead of as a single-user because upon installation, Adabase will store your program files and user files in separate folders. While this is true, I don't think people are as confused over what type of computer setup they have or should use, as much as what security protocals to use with AdabaseD. In other words, if you installed AdabaseD for "single-user", DON'T ADD AN ADMINISTRATOR USER NAME OR PASSWORD! In fact, DON'T click on the "Administrator" tab at all on the Database Properties dialog box when creating a new database. The Administrator user name and password is taken from the User Name and password for single-user installation. Therefore, the Administrator feature is not necessary for single-users. (By the way, the installation instructions are confusing when discussing these security measures. In fact, during the install, there isn't a choice to make between "single-user, network user or workstation/client"...at least, it didn't prompt me for a choice during installation. I learned what to do from reading both the "Star Office User's Manual for SO5.1 and the Star Office 5.2 Companion. Information from both manuals clued me in as to what NOT to do when creating a new database as a single-user. Most of my problems with AdabaseD were derived from adding an Administrator user name and password when I didn't have to, yet the instructions continually refer to entering these features. Again, for single-users, skip this step; you don't need it!)
5) A Functional Database. You'll know your AdabaseD is working properly when the little traffic light next to your clock is "green." If it indicates red, you need to check your path, security protocals and overall installation before you can proceed. If it indicates yellow, your installation was fine, but your security protocals are wrong. Generally, this means you entered the wrong user name and/or password, or you're not "connected" to your database. (Note: For me, my problems was that I entered both a user name/password and an Administrator user name/password when I didn't have to. I got them so mixed up, even I couldn't remember what I'd enter. So, take a lesson from me: Write down your user name and password, and once again leave the Administrator user name and password alone for single-users). As far as connecting to your database, usually this is accomplished when you first create a new database. You can disconnect from a database by right-clicking on your database icon and checking "connection". You should be able to reconnect to your database by right-clicking on the traffic light and checking "restore". (Note: I'm at work and posting all of this from memory, so I may not be 100% on this part. I'll verify this tomorrow and make revisions, as necessary.)
6) Other Important Issues. SO5.2 uses AdabaseD, version 11 while SO6.0 uses version 12. Since Sun has initiated their End-of-Life (EOL) policy for SO5.2, it's doubtful version 11 will be available except by purchasing SO5.2 either directly from Sun, or from a local vender, i.e., CompUSA (see SunMicrosystem's webpage for details on the EOL policy for Star Office 5.2), or by contacting the USA distributor for AdabaseD. Go to the following website for details on distributors:
http://www.softwareag.com/adabasd/adabasd/Distributors.htm
If you're interested in downloading a copy of AdabaseD, version 12, go here:
http://www.softwareag.com/adabasd/adabasd/AdabasD12.htm
Two Words of caution: a) I don't know if version 12 will work with SO5.2. Contact either SoftwareAG or the USA distributor at the website listed above for details and instructions; b) The download file is a zip file and may take a while to download. Again, do it overnight if you must.
There you have it! Lots of info you probably never even knew until now. Adabase is actually very good once you get it working properly. Now, if I can only figure out how to set the properties to a subform, I'll be in business! I can create the main form and add a subform, but I haven't figured out how to set the separate properties. So, if someone can help me out, I'd greatly appreciate it.
Lee Brown
I won't recommend creating a new database in a separate "Database" folder on the task bar. For some reason, Star Office views new databases created outside the Explorer as icons. You can't expand on an icon, hence the "+" sign doesn't appear next to the database name. Now, you can still work with your new database if you created it in a "Database" folder, but the object folders will appear in the Star Office Desktop. You'll have to double-click the object folder you want to use then create the object as normal. Navigation through your database is a bit more touchy this way, but it can be done once you orient yourself to a new way of doing business.
That's if for now!
Lee Brown
Nils Homp - Sun StarNews Support
I am very glad to hear that you finally got it working even though it
was a seemingly time consuming procedure. I am sure the additional notes
you have given will be of great use to other fellow users of
StarOffice/Adabas as they are quite extensive indeed.
Regards,