Replies

Hi Jim,

I’m not sure about your custom dictionaries and autocorrect entries, but one thing that has helped me through many rebuilds is the Office Resourse Kit utility. This has allowed me to save my settings for EVERYTHING in office – toolbars, preferences, even the infamous Office Assistant.
After downloading and installing these tools, just run the Office Profile Wizard. It will save your settings locally into an OPS file (different from the internet-based Save Settings feature Microsoft pushed through the OfficeUpdate website). It will also give you the information you need to have these settings added to your new install of Office 2000 on your new system.

An additional note: I’ve used the Custom Install Wizard quite a few times and it REALLY makes re-installing a breeze!! It allows you to save all of your install preferences so that future installs can be completely automated. It’s worked great for me.

Here’s the link to the ORK toolkit (it’s 8.9 MB):
http://www.microsoft.com/office/ork/2000/d…ad/ORKTools.exe%5B/url%5D

HTH
-MarkJ-

I’m sure there are better ways to do this, but here’s the code I’ve used successfully in the past:

Dim appAccess as Access.Application
Set appAccess = CreateObject(“Access.Application.8”)
appAccess.OpenCurrentDatabase “C:MyPathMyDatabase.mdb”
appAccess.DoCmd.OpenForm “MyFormName”, acNormal
appAccess.Visible = True
appAccess.UserControl = True
appAccess.DoCmd.RunCommand acCmdAppMaximize ‘This maximizes the window

Note: This was for Access 97. It should work in Access 2000 with no problems, except you’ll need to change the version number to “9” for CreateObject(“Access.Application.8”).

HTH
-MarkJ-

Need help simulating a corrupt memo field? Try unplugging the network cable from a machine while the record is being saved from another machine. That should do the trick!

-MarkJ-

Hi Gary,
Yes:
-File|Get External Data|Import…
-(Select the database to import from)
-Click the Options>> button
-Select the “Menus and Toolbars” checkbox

That should do the trick (this is the same in Access 97)

HTH
-MarkJ-

Hi Steve,

First, you don’t really need to store the values for City and State in both tables. It sounds like a good idea to store the City and State in the ZIP tables (along with the Zip Code). That way, all you’ll have to enter is the Zip code and it will look up the City and State. It’s also more efficient as far as size goes – only storing the City and State once rather than twice; and not to mention the fact that it prevents human error of mistyping a city name…

With that said (and after backing up the information), I would delete the City and State fields from your Customers table, keeping the Zip Code field. You’ll want to set a one to many relationship between the Zip Code fields in both tables (ZIP being one and Customers being the many). This can be done in the relationship window (Tools|Relationships) – add both tables, drag the Zip Code from one table to the other, select “Enforce Referential Integrity”, then create the relationship.

Keep the City and State fields on the Customers form, but rather than binding them to a field, assign the Lookup statement in the Control Source property for each field. Something like the following should do the trick:

City:

-MarkJ-

If I understood your post correctly, you can use the Save Record command on the Exit event of the form:

Private Sub Form_Exit()
DoCmd.RunCommand acCmdSaveRecord
End Sub

HTH
-MarkJ-

I just thought I’d throw my $0.10 in….

Remember that Access can handle individual tables as large as 1GB. That’s a LOT of data!!!

But I agree speed is certainly not taken into account there…

-MarkJ-

In addition to importing objects into a database, you’ll have to manually restore any code references the old database used. You’ll first need to get a look-see at the references used by the old database.

Then open the new database, switch to the Modules tab, and open any module (doesn’t matter which – just to get to the module editing menu/toolbar). You’ll find the References list under the Tools menu. Just select the ones that were selected in the old database and unselect any that weren’t. I always re-compile my projects when I move my objects around (Debug|Compile and Save All Modules).

Just a note: It sounds funny that the CHR() function was not working – it’s part of the VBA reference, which is referenced by default.(Hmmmm…..) So, if the above suggestion doesn’t solve the problem, it could be something deeper.

HTH
-MarkJ-

It’s generally a good idea to store First names (or initials) and Last names in separate fields. It helps keep things cleaner and more optimized in the long run – not to mention that it follows the rules of Data Normalization.

I realize it may be more work to enter two fields, but it’s usually worth the extra trouble to have them separate.

When you need to sort by last name and first initial (if present) you could use a query. The field could read something like….
CompleteName: IIF([FirstInitial]=””,[LastName],[FirstInitial] & “. ” & [LastName])
-where [FirstInitial] and [LastName] are your fieldnames for the appropriate fields. This statement will check to see if there is a first initial entered. If so, you’ll get something like: J. Doe. Otherwise you’ll just get Doe.

If you decide to use a field to sort alphabetically you’ll need to modify the syntax to put last name first, then first initial.

HTH
-MarkJ-

Thank you all for your most helpful suggestions.

I definitely agree that it’s quicker to use the Integer to loop through large collections rather than the Variant, although there are times when the Variant is necessary.

I found the webpage article by Ken Getz (suggested by Scott A) very informative. Its level of detail far exceeds my current needs, but very helpful nonetheless.
Here’s a link directly to the article:
http://www.microsoft.com/officedev/articles/movs101.htm%5B/url%5D

Again, many thanks!

-MarkJ-

You’ll want to create a shortcut to the database and add “/RUNTIME” to the end of the database name. The target of the shortcut should read (for example):
C:MyDocu~1MyData.mdb /Runtime

HTH
-MarkJ-

Maybe you could use the NZ() function. It converts a null value to Zero (or any other specified value). You can place it in your query as follows:

Field1: NZ([FieldName])
OR
Field1: NZ([FieldName],0)

The on-line help in Access will give you more information about the syntax and arguments.

HTH
-MarkJ-

DOH!! I kept playing around with it and found the answer to my own question.

The /RUNTIME switch is correct for starting Access in Runtime only environment. But apparently you need to have Office Developer installed for this to work properly (I think).
I have Office Developer 2000, but not 97 – which is the format of the database I was testing.

I guess I’ll convert it to 2000 just to make sure it runs under the run-time environment.

Thanks for taking time to read this rhetorical and somewhat confusing post.

-MarkJ-

I just discovered this function while browsing the code librarian (that comes with MOD 2000). I haven’t had a chance to test this yet, but it looks like it will do the trick. It appears that the menu item MUST be a command button rather than just menu text. Here is is:

‘
‘ Checks or Unchecks a menu item depending on value of
‘ boolCheckIt argument. Set it to True to check, False to uncheck,
‘ and leave out to toggle.
‘
‘ NOTE: There is no way to programmatically add a checkmark next to a
‘ built-in menu item; you can add checkmarks only to custom items.
‘ Checkmarks for built-in menu items are controlled by the parent
‘ application, and your code will result in the error:
‘
‘ “Method ‘State’ of Object ‘CommandBarButton’ Failed”
‘
‘ Calling convention:
‘ CheckMenuItem “MyCommandBar”, “MyMenu”, “MyMenuCommand”
‘ CheckMenuItem “MyCommandBar”, “MyMenu”, “MyMenuCommand”, True
‘ CheckMenuItem “MyCommandBar”, “MyMenu”, “MyMenuCommand”, False
‘
Dim cmdMyMenuCmd As CommandBarControl
On Error GoTo errCheckMenuItem

Set cmdMyMenuCmd = CommandBars(strMyMenuBar).Controls(strMyMenu).Controls(strMyMenuCmd)

‘ Verify this is a button control.
If cmdMyMenuCmd.Type msoControlButton Then
MsgBox “The command bar control must be of type msoControlButton.”
Exit Sub
End If

If IsMissing(boolCheckIt) Then ‘Optional arg missing, so toggle.
cmdMyMenuCmd.State = Not cmdMyMenuCmd.State
Else ‘ Check or uncheck depending on value of boolCheckIt.
cmdMyMenuCmd.State = boolCheckIt
End If

exitCheckMenuItem:
Exit Sub

errCheckMenuItem:
MsgBox Error$
Resume exitCheckMenuItem
End Sub

HTH
-MarkJ-

I would also add that it (always) helps to compact the database before copying to the floppy. The database gets bloated as it is used and compacting purges any temporary objects and makes the file as small as possible – short of using compression (like ZIP).

Access 97: Tools|Database Utilities|Compact Database
Access2000: Tools|Database Utilities|Compact and Repair Database…

HTH

-MarkJ-