Replies

As jacksonmacd said, you won’t have the benefit of the permission structure built in to Access if you only make use of the Windows login information, but you can still lock things down reasonably tightly if you force the users to use your forms and don’t allow them to get directly to the tables themselves; just check the windows login information before doing anything “secure”; you can even make command buttons only appear if the user is supposed to be able to use the buttons (by setting the visible property) and make fields in your forms read-only or invisible as needed. Beware of people getting around your security by simply importing into a new database though (that might not be an issue for you since you indicated that you have a SQL Server backend).

Any possibility that the messages are getting blocked as spam further up the line? The ISP that I use for my home e-mail has its own spam blocker that I can set to allow, flag (i.e. prepend a warning to the message subject) or block spam sent to my account; if spam is blocked at my ISP, it never gets to my e-mail program in the first place. She could check with her ISP to see if that is the problem, and if so, whether she can change how messages to her account are handled.

Yes, it can be wrong by a day occasionally. Remember that a calendar year is NOT 365.25 days; it is 365 days 3 out of 4 years and 366 days 1 out of 4 years (I’m ignoring the “century rule”). The Access help provides an accurate age calculation –
=DateDiff(“yyyy”, [Birthdate], Now())+ Int( Format(now(), “mmdd”) < Format( [Birthdate], "mmdd") )

I don’t have a specific answer to your question, but you do realize that there is NO dependable way of knowing for certain whether someone has read a message, don’t you? Even if you turn on the read receipt option when you send messages, the recipient can still prevent the receipts from going back (and many people do block them).

Why would having the extensions showing give you conflicts with the names? The only issue I can think of is that when you are renaming you need to be careful not to change the extension unless you really mean to (not useful to change an Access database extension, but VERY occasionally it can be useful with other programs). However, since Windows will warn you if you try it’s not much of a danger.

If you mean that on one computer you have a file named blah.mdb and on another it’s just named blah, just remember to ignore the extension when telling someone what a file is called (or alternatively, tell the others to ignore any extensions you mention if they don’t have them showing on their computers).

If you really insist on living dangerously, in any folder window go to Tools | Folder Options in the menus and click the View tab. Check the “Hide extensions for known file types” box. However, as HansV said, that leaves you open to nasties.

I wonder if the format(…) is trying to format a number, and getting confused? Try substituting
iif(len(ar(i))=1,”0″,””) & ar(i)
for your format(…) call.

Has the operator tried bypassing the Switchboard before? I’m wondering whether he’s holding down the shift key at the wrong time. I do that periodically in my more klutzy moments; Access is VERY quick about checking the status of the shift key after you double-click an unsecured database or click OK to the id and password prompt in a secured database, so if the operator tries to hit the shift key AFTER he double-clicks or clicks OK it won’t help.

If you also set the default for ID to 1 you don’t even have to type that value into the record (I know that doesn’t save keystrokes for a single table, but might be handy if you use the table as a template for other 1 record tables).

One more suggestion to add to all the others; be extremely careful of phishing attacks. NEVER EVER provide account information in response to an e-mail even if it is supposedly from a bank or other financial institution, and NEVER EVER click any links in e-mails that are supposedly from a bank or other financial institution (even if the e-mail “looks like” an official e-mail) – enter the institution’s address yourself using the address bar or your favourites.

In addition to what HansV suggested, if your TRType field is on the tabbed form (presumably on one of the pages that is always visible), you’ll probably want to put the same code in the After Update event of the TRType field so when the type is entered the appropriate pages immediately disappear.

If you mean you ONLY get a new record (i.e. no existing record), then, as HansV suggested, the Data Entry property in the form might be on. If you meant that you get the record you want AND a new record, turn off Allow Additions.

Impossible to tell, particularly if the recipient isn’t also on hotmail (and even if he is, I can think of a possibility or two). A server en route to the recipient could have crashed and lost messages. Something could have happened at the recipient’s computer. Your message might have “looked like” spam and got sucked into a spam filter. On days when the deluge of spam is particularly bad, I’ve been known to accidentally delete messages that it didn’t intend to because they’re in the middle of a mass of spam messages (I sometimes notice that I’ve done that if I happen to glance at my deleted items folder). Recipient might have his e-mail configured incorrectly so you don’t have the correct return address – have you sent him messages successfully before?

With all the e-mailing worms out there, you can’t trust any more that you will get an undeliverable message for messages that are undeliverable.

When you are writing VBA code for a form or report, me is used to point to the form or report that your code is running in. Quoting from the help, “The Refresh method immediately updates the records in the underlying record source for a specified form or datasheet to reflect changes made to the data by you and other users in a multiuser environment.”. Hence me.refresh runs the refresh method for the form your code is running in. See also repaint and requery.

If you need to do something after the popped up form closes (whether that be refreshing if for some reason it’s necessary, or anything else), make the popped up form modal. Execution then won’t continue in the underlying form until the modal form closes or is made invisible, and you can then do me.refresh or whatever else is necessary.

I agree with HansV – sounds to me like you have the Locked property set to Yes, but somehow you neglected to set the Enabled property to No. I don’t believe SteveH’s suggestion of turning off the Tab stop property will make any difference – my databases have lots of locked fields, some permanently locked and some locked and unlocked in code, and I don’t think I have ever played with the Tab stop property – if a field isn’t enabled there’s no way you can tab to it.