Recent content by BadSikander

That's exactly what I needed. Many thanks for your help.

Hello. Thanks for the replies. I am trying to artificially populate a map with markers representing my data. On my main form I have an image of a map. Placed over the map at the correct geographical locations are forty invisible, unbound text controls, each representing one of the forty...

Hello. I'm not very good with lookups, but from a button click I need to check what record ID's are found in a query, and then carry out different actions for each one that is present. The query contains minimum zero records and maximum forty records at all times. I am doing this currently...

Is it not standard practise to keep your queries in the FE of a split database? Presumably if only a system password can prevent Excel importing information from Access, then you need to always apply a system password to your FE? Otherwise queries can be imported to Excel from the FE, and bring...

OK, reluctantly will have to split DB and password protect BE. But users are on remote sites with their own network / drive mapping etc, so they will have to link the FE to the BE themselves and I still don't want them knowing the password when they do that. There seems to be no way to...

That certainly prevents importing / linking from Access, but Excel still seems to be able to see and retrieve the tables.

Hi. At this stage the db is intended to be a read only resource that individuals save on their desktops. They are being advised not to save to shared / network drives.

Thanks for the reply. Unfortunately, this database is going out to numerous sites on different networks. So to have it FE / BE would be a last resort only. I would still have to hand over the password so users could link FE & BE correctly. Either that or go out to every site individually to set...

Hello. I have an unsplit Access 2003 database. I don't want people to be able to link to its tables or import them into other databases, Excel, etc. I know I could "lock" it with a database password, but I don't want users to have the inconvenience of typing this in whenever they open the...

Good idea. Will do that. Thanks.

Great, I'll give that a try. Thanks for your help

That certainly looks the quickest way if I have to change the individual forms themselves, thanks. Probably a stupid question, but what does the 'acSaveNo' bit do? Tell it not to save the record? If so, will it still close the form if I just leave that bit out? And does the same format work...

Hello. Only by changing the code on every form and every event where a msgbox might be called and cause this problem. I expect that's what I'll have to end up doing, but I was just hoping there might be a way to prevent the timer event itself running to save some time. Thanks though

Hello. The timer event does a dlookup against a query. The query uses information from a field on the background form in its criteria. If it finds any records in the query, a popup form appears and warns the user. If it doesn't find any records (which is 99% of the time), nothing happens...

Ah, but I would have to make that change for every single one of my forms, and for every call to msgbox. The shift of focus problem with msgbox doesn't just affect DoCmd.Close, but delete commands, requery, etc. so it's a lot of instances to find and amend. That's why I was hoping I could...