Replies

Does the PowerPoint interface (toolbars, title bar, etc.) display colors normally?

If not, you may have inadvertently turned on High Contrast mode. Activate the Accessibility Options control panel, activate the Display tab and make sure that the “Use high contrast” check box is clear.

Otherwise, there might be something wrong with your installation of PowerPoint. You can select Help | Detect and Repair from within PowerPoint to see if that will get rid of the problem.

Hi, Hans,

The menu and toolbar appeared fine in my Powerpoint. Detect and Repair helped to restore my Powerpoint. Thanks to all of you who responded to my post. I am still puzzled how suddenly the problem occurred without warning.

Does the PowerPoint interface (toolbars, title bar, etc.) display colors normally?

If not, you may have inadvertently turned on High Contrast mode. Activate the Accessibility Options control panel, activate the Display tab and make sure that the “Use high contrast” check box is clear.

Otherwise, there might be something wrong with your installation of PowerPoint. You can select Help | Detect and Repair from within PowerPoint to see if that will get rid of the problem.

Thanks, Hans. The desktop concerned is in the office. It is Saturday here. I will definitely try it out when I get back to the office on Monday. I will tell you the result of my trying.

What happens if you experiment with different background colors for the slide?

Hi Hans,

The background colour didn’t appear, but in the thumbnail and slide show, it is okay.

Thanks for your help, John.

Microsoft said in the the knowledgebase that the dialog box kicked in on starting Visual Studio 2005. My Visual Studio 2005 started fine. It is on starting Microsoft Office 2000 that the Windows Installer popped in.

The article also mentioned that it was due to improper installation of Visual Studio 2005, resulting in a problematic mso.dll. I checked the properties of the mso.dll file in the stated folder. Mine is a Microsoft Office XP with version 10.0.3501. But I am using MSO 2000. Is there something not quite right? I do not try repairing Visual Studio 2005 as it is working flawlessly. Shall I repair MSO 2000 instead? Any pointer before I plunge in?

tblMain and tblSub are two tables related by ID (one-to-many relationship). The tab control essentially displays data from tblMain but with the last page displays data, if any, from tblSub. The tblMain is actually the student info and tblSub indiscipline records, one indiscipline kes one record. I want to add records of indiscipline of a particular students if there is one. Am I not using the query correctly?

My form has a Tab control with 5 pages. The Tab control is populated with SQL “Select * from tblMain Inner Join tblSub on [tblMain].[ID] =[tblSub].[ID]”. On the last page is a subform with the Link child filed ID and Link master field tblMain.ID. The record source for the subform is “Select * from tblSub”

I can navigate to all the pages with data from tblMain. However when I activated the tab page with the embedded subform and tried to enter some data, I could not go to another tab page and was stuck at the tab page with the subform until I exit the program.

With this sketchy description, can anyone tell me what is (are) the possible reasons?

Using HyperlinkAddress is simpler but it has one caveat : the message text is in a single paragraph only; whereas by using docmd.SendObject, I can add vbCr in my message text to break it into several paragraphs.

I found the solution after searching the internet. I changed my label into a command button, and add in the code

DoCmd.SendObject acSendNoObject, , , strEmailAddr, , , strSubject, strMsgBody, True

The boolean parameter True is to enable user to edit the email message. Take note of the parameters which are left blank. The solution may be helpful for anyone who may have the same problem as me.

(Edited by HansV to make URL clickable – see Help 19)

Thanks HansV, Charlotte & Wendel for your valuable responses. Since it is confirmed that there is no quick fix for my problem (I was hoping there was one), I looked into the structure of a dBase file and I managed to solve my problem though in a convoluted way. I put it down in case there is someone who may need this info in future. Here is my solution:

(1) Get a description of dBase file structure. One can get it, for example, from here for dBase III+ to 5. dBase 7 has a different strucuture.
(2) Make a copy of the dBase file and work on the copy.
(3) Get record number from bytes 4 to 7.
(4) Get record length from bytes 10 to 11.
(5) Open the dBase file with a hex editor to find out where the first record begins. The first byte of the first record varies with available record fields. My database is all text and of fixed length.
(6) Loop through the records to check if the first byte of each record is a * . If it is, then it is a record marked for deletion and replace it with a space. I attach a * to the end of of the value of an available field to signify it is a record marked for deletion. I can’t manipulate the dBase file in VB6 by adding a new boolean field to indicate deleted records without losing the info on records marked for deletion.
(7) Save the newly modified copy of dBase file.
(8) Use SQL to insert the modified dBase file into the Access database. Loop through the records again to look for * at the end of the field in (6). Delete the * and register the boolean field in the Access database correspondingly. One may lose a byte of information if the field in (6) is filled up to the last byte. Choose the most dispensable field with spaces.
(9) Finally delete the modified dBase file as well as detach any linked tables as needed.

All the procedures are done in VB6 and the codes are actually very short and fast too.

Excuse my naivety. I’m just thinking along this line : a record marked for deletion in dBase begins with a ‘*’. Can we parse the records for the ‘*’ and just omit it?

Perhaps I see some light, Hans. You said we couldn’t do it “directly”. Can you suggest method(s) that I can do it indirectly or in a round-about way?

My solutions to my clients are these (both not satisfactory):
(1) Undelete the dBase III records marked for deletion in the original DOS program (Clipper 5.3) and then import them into Access (VB6 program). Then delete them again in the VB6 program by changing the boolean field to TRUE..
(2) Re-enter the records marked for deletion in VB6 and then mark them for deletion by setting the boolean field.

Your suggestion is good but my clients may not know dBase well enough to do it. I am looking for some parameter settings in SQL or some identifiers to detect dBase records marked for deletion when importing from dBase to Access so that my imprt codes can do it automatically without users’ intervention. Look like I am out of luck this time.

Thanks for your help, Hans. You had helped me out of my cul-de-sac a few times previously.

Thanks, Hans. I downloaded the program VB6Cli.exe which solves the SSTAB’s license problem. I still wonder why suddenly the license info disappered. Corrupted registry? What does VB6Cli.exe do which regsvr32.exe fails? I just wonder.

Now the VB IDE at its pleasure terminated abruptly while I was editing the codes with the error signature like

AppName: vb6.exe AppVer: 6.0.97.82 ModName: unknown
ModVer: 0.0.0.0 Offset: 5d324347

The problem is it didn’t happen every time.

I am using VB6 under Windows XP SP2.

I browsed through the folders in the computer with problem and discovered that MS Access 2000 was actually installed but somehow was corrupted. Since the original Office CD wasn’t available, and Access wasn’t working anyway, I took the drastic action of deleting all occurences of DAO 360 in the registry (op! Heaven forbids). I reinstall my VB6 program and this time it worked but still not properly. There were times like error “3264 – No field defined: cannot append TableDef or Index” which never appears in aproperly installed program.

I deduced that the fault lies with the particular system. My installation program thought that DAO 360 was installed (which it wasn’t or was missing from the computer) and didn’t install the DAO 360, causing a lot problem to my program. I assumed my program would work correctly once the mess with corrupted Access 2000 was cleared with re-installation of MS Office. Is my deduction logical?