a 2nd user (maybe a Secretary)

[sagamw]

Hi guys, Happy holidays to you all !!!

I have finished my db (a project I started a few months ago) and I am very happy with it! A few people I showed it, were very impressed by it's design and functionality and I am now thinking of selling it to the public (here in my country at least).

It's a "program" (an access db actually) with many functions useful to my profession, but also with something like an appointment diary. It's much different than let's say MS Outlook but for my line of job, it's all we need.

Anyway, to my question: Because of this functionality (the appointment book) comes up the need to be able to access this form (the appointments) from another PC that it's in the office of a secretary. So the scenario is: The manager has the main db in his PC, and his secretary has a 2nd PC connected with the 1st PC, in a network (I don't know wifi ad-hoc, or Ethernet etc.). How can the 2nd PC have access to the db and add/modify appointments in real-time when simultaneously the 1st PC is using the db?

I don't want to use SQL Server 2008 or anything like that.
Any ideas on how this can be accomplished?

 

[dhookom]

Typically the application should be split into front-end and back-end mdb files. If your's isn't, don't even think about selling it since you will have issues updating your code, reports, queries, etc.

The back-end containing only the tables should be located in a shared folder. Each user should have his/her own front-end. Wifi isn't generally recommended for Access databases. You might want to consider SQL Server Express.

Duane
Hook'D on Access
MS Access MVP

 

[sagamw]

Hi dhookom.

Yes I am aware of that. I have already split my db. (it's an easy thing with Access 2007 after all)

So your suggestion is to have 2 copies of the front-end (PC1 and PC2) and the tables (back-end) only to PC1? The secretary PC2 will have access adding appointments without "interfering" with the use (simultaneously) of the db from PC1?

P.S.2.: If I am correct then can I build a LIGHT version of the front-end with ONLY the appointments form just for the PC2?

And another thing: When you split the database (as I recall because I'm not in front my "Access" PC right now) and you move a copy of your front-end to another path/folder/drive/pc It asks you to point where the back-end is.
How can be done seamlessly (I mean installation wise).
I read how can I make an installation (runtimes, Package Solution Wizard etc) but how can this be done for the 2nd PC? (without "searching" for the tables afterwards)

P.S. I checked some things about SQL server (Express OR the other things that costs ...25k!) when I realized the 2GB limit for the attachments. I found it somehow confusing. That's why I changed by approach for this in my db.

 

[dhookom]

SQL Server Express is a free download. There are lots of resources on the web that provide the code for automatically relinking Access tables.

I believe your understanding of splitting and running the application is correct.

Duane
Hook'D on Access
MS Access MVP

 

[jrbarnett]

If you built this system on company time, using company equipment (including internet access and software licenses) then the product belongs to your employer, not you.
If your company are happy to sell this, then that is fine, but they should reap the rewards.

John