Replies

maybe this drilldown check procedure will help to determine the source of the error:

1. at the computer where you created the template with the toolbar (this should be your homecomputer, inferring from your 1st post):
– start word with the /a switch to open it without any add-ins loaded and without the normal.dot (windowskey + R, in the run dialog that shows type winword /a and press enter)
– now open your template and go to the organiser:
if you see the toolbar listed, all is ok there (are all the buttons present?)
if not, you somehow didn’t attach the toolbar correctly to the template.

there’s a remote chance one of the add-ins is resetting every toolbar, or disabling custom toolbars (also see point 2), the /a switch will show you if that’s the case

2.
– what is the name of the toolbar?
– is it a completely new toolbar or does it modify another toolbar?
– if it modifies another toolbar, is the source toolbar also on the destination computer? is it enabled? does it modify a built-in or a custom toolbar?

3. repeat step 1 for the destination computer.

if the toolbar was listed at your homecomputer, but not at the destination, then maybe it got lost in the emailing process. check the security policy (firewall and stuff) with the people you are sending the template to. does your template contain macro’s, then check if these are available at the destination computer. if this is not the case, than the security policy becomes more of a candidate for losing your toolbar. (maybe the firewall messes with your template, stripping out macros, messing up your template so much toolbars are also lost.)
you can check this yourself at work by mailing a template with a toolbar to for instance a hotmail address and mailing it back from there to your work.

let us know how you get along.

greetings,

hi,

did you create this tooolbar yourself? make sure before you create it that you select the template in the save in: combobox in the customize dialog (of which the prgrammatical equivalent is the customizationcontext property), or use the organiser to move the toolbar to the correct template.
another possibily is that this template was originally placed in the startup directory of word and creates its toolbars on the fly when it is loaded. In that case, save it to the corresponding directory of the computer you mailed it to and then it should recreate the toolbar.

greetings,

hi Beryl,

if i’m not mistaken and looking at your setup and the arguments of your find, it seems the procedure below will do what you want, without a find:

Sub FindFeb01_pj()
Dim oCell As Range
For Each oCell In _
Range _
( _
Sheets(“Feb”).Range(“a1”), _
Sheets(“feb”).Range(“a65536”).End(xlUp) _
)
If _
IsNumeric(oCell) And _
oCell.Value > 0 And oCell.Value < 32 _
Then
oCell.Offset(1, 0).Range("A1:C3").Name = "day" & oCell
End If
Next
End Sub

greetings,

hi Dennis,

format->cells…->alignment->text alignment (horizontal)->fill.

greetings,

hi,

goto start->all programs->microsoft office tools->office XP language setting tools
disable all support for far east languages.
(ofcourse you also have to uncheck tools->options->view->text boundaries in word itself.
i suppose this is a bug, maybe there’s a registry tweak to allow far east languages support without the crop marks.

greetings,

hi Hans, Melanie.

formatting the data in excel that will be transferred to word, works for me in office XP (using the DDE merge option), no need to create extra columns.
btw, wether the transferred number is the result of an excel formula or hard coded, wether you’ve applied the number format directly or used a custom number format in excel, it still is tranferred as displayed in excel when i test it. (maybe this indeed won’t work if one would try the odbc or other merge options that are available)

greetings,

hi Melanie,

that’s the problem with professors, they always want to be too precise!

seriously though, you have two options.
the simplest is to format the numbers directly in excel. word will show them exactly as they are displayed in excel.

or edit the mergefields fields in word. you’ll need to add a formatting switch:
{ MERGEFIELD numbercolumn # #.##0,00 }

the formatting switch # #.##0,00 will tell word to round numbers to the second decimal. beware of internation settings, you may need to switch comma and the decimal point.

greetings,

thanks Kevin and Klaus,

somehow i was temporarily unaware of the findcontrole().execute statement. your posts proved an excellent reminder!

greetings,

hi Bryan,

that seems logical. the dialog collection only contains thos dialogs for which there’s a dialogconstant.
in the mean time i’m running a loop which displays all dialogs and crashed word several times already in the process.
it has come up with the strangest things (launching office application, help, showing tooltips, displaying a splash screen for MS schedule+ (!)), but the dialognumbers for the dialogs mentioned in previous mail remain elusive…

greetings

hi Klaus,

aha now that’s interesting! do you have by any chance a complete listing of dialogs for which there is not a corresponding dialog constant.
for instance
– the edit find dialog, but with all tabs enabled?
– the add watermark dialog (format->background->printed watermark…)
– ….

i’m running the numbers right now but they haven’t come up yet.

greetings,

hi Ken,

for this reason, it is good practice to force explicit declaration of your variables with Option Explicit on top of each module. this will signal you of each non-existant or mispelled variable before you can run the code. I always do this myself, and i also always declare them with a capital somewhere in the name so you can see intellisense changing it after you’ve confirmed the codeline with enter. you’ll notice immediately you’ve made a type when tha capitalization doesn’t happen.

you can also set ‘Option Explicit’ in the VBE options, so you don’t need to type it yourself. just check ‘variable declaration required’ (transl. from Dutch)

greetings,

hi Bjorn,

Application.Run MacroName:=”FileProperties”

is the only possible way i believe.

greetings,

hi,

search for *.xlb files and copy them to the same location.

greetings,

hi Roberta,

this was the code i am referring to in my post – well done!
replace
.Range(“A2”).CopyFromRecordset rs
with
.Range(“A65536”).end(xlup).offset(1,0).CopyFromRecordset rs

and you’re done!

greetings,

hi Rob,

sure. insert a keypress event for the textbox you want to validate:

Private Sub TextBox1_KeyPress _
(ByVal KeyAscii As MSForms.ReturnInteger)
Debug.Print KeyAscii
Select Case KeyAscii
Case 65 To 90, 97 To 122
Case Else
KeyAscii = 0
End Select
End Sub

the above event will only allow a-z, A-Z keys. i inserted a debug.print keyascii which sends every keycode to the immediate window also, so if you would like to allow an exlamation mark to be typed also, simply go to your textbox and press an exclamation mark, go back to the immediate window to view the code for this key and add it to the case structure. after you’ve added all the keys you want to allow, comment out or delete the debug.print codeline.

greetings,