Search results

Thanks for all of your replies. They were very helpful. I've initially gone with The_Doc_Man's suggestion and created foster parents for the orphans and resolved to keep a closer watch for reoccurrences. ......so far so good.

As a volunteer I built and maintain an Access database for a charity. It's front end back end configuration and the back end is stored on their office server. Users connect via a VPN and Microsoft remote desktop. Among other functions the database records 1 to 1 contacts with clients and also...

Thanks Guys. Pat's suggestion looks promising, and I should have done something like that at the beginnning. I've got about 30 named non-sharing users though, so I think in the first instance I'll try renaming the shared FE file and see who yells. Then if there are more thn a couple. I'll...

A fair point.

Thanks for the suggestion. Part of the problem is that their network is maintained by an IT contractor, who administers the network. Whenever I'm asked to add a new user, byt that user or their manager, I have to ask the contractor to create a named folder in an area I can access. I then place...

I'm a volunteer supporting a local charity remotely. I have built them an Access front/end back end CRM, which has been in use for several years now on their LAN with both in house and remote users. Most users have their own dedicated front end in their own named network folder, but I know that...

Hi Lightwave, I've used that suggestion in one locality, quite successfully. So thanks for that. I take gemma's point about local tables in the front end copies. I'd never considered that danger. Thanks again. Cheers, Tommac

Thanks for the suggestions. I'll certainly give them a try. The thing is I have a dozen or so small databases residing on a server and the users currently access them via shortcuts on their desktops, so I didn't think I would be increasing network traffic any more than it is now. The users...

Apologies if this is an old chestnut but I can't find any previous reference... the books recommend always splitting networked access databases into front end/ back end versions to avoid data corruption if a client pc crashes. However its a bit of a pain having to install the front end on many...

Thanks, One table it is then. Regards, Tommac

Thanks for the comments and all of the very useful links. One query though, I was going to keep the different types of jobs in separate tables(tblHandymanJObs, tblMiniBusHire etc.) linked one-to-one, with the ServiceRecordID in the record_of_service_table because each type of job has very...

Here is what I'm thinking so far. The original db has been built by someone else, but it has reached the limits of their design. I'd like to be sure that my proposals are likely to work, before I dive in and make radical changes. zipped.doc file attached ( I hope). regards and thanks in...

I am a retired computerholic, who spends most of his days messing around with Access. I started about 10 years ago at home, as I've always been fascinated with the power of databases and the challenge of programming. I then got involved in volunteering with local charities in North East England...

Can anyone advise on the best structure for the following situation please?: I have been asked to look at an access datatbase for a local charity which receives enquiries for services such as doing laundry, performing household tasks etc for elderly/infirm people. The database has been built up...

Why not install Microsoft terminal services server on a new server alongside the one which runs the database back end? In my (limited) experience Access works well like this over ADSL links to the remote clients, as the only data which is passed to the remote clients are screen updates and key...