Questions For MVP

[Rayrock]

I have a unix system running my warehouse inventory control and accounts
recieveable. Probelms with high costs that our current software vendor
charges. Updates, and minor changes...

I want to switch to windows for many reasons. The most important I want
control and lower costs. I'm fairly decent with Access.

Questions?

1. Does access support 6 people using the same database?
2. Can I run the access Inventory system on Windows XP pro or should I Step
up to server 2003?
3. If I need Server 2003 Do I have to be a seperate version of 2003 for all
machines?
4. Is there a templete that can be used for starting point?
5. Is there migration software that convert my exsisting unix Inventory
system?
6. If I setup my system on a windows base plateform would I be able to set
up IIS so I can create a website that would show current inventory through a
designated IP address?

These question my be indepth for the group sorry dont know where elese to ask?

Ray

 

[Allen Browne]

Answers embedded.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I have a unix system running my warehouse inventory control and accounts
recieveable. Probelms with high costs that our current software vendor
charges. Updates, and minor changes...

I want to switch to windows for many reasons. The most important I want
control and lower costs. I'm fairly decent with Access.

Questions?

1. Does access support 6 people using the same database?

Yes. A couple of dozen users would be no problem.

2. Can I run the access Inventory system on Windows XP pro or should I
Step
up to server 2003?

XP Pro would be fine. Split the database into a back end (tables only), and
front end (linked tables, queries, forms, reports, and code). Give everyone
their own local copy of the front end. The back end mdb could be on in a
shared folder on one of the workstations with no problem (i.e. a dedicated
server is not required).

3. If I need Server 2003 Do I have to be a seperate version of 2003 for
all
machines?
N/a.

4. Is there a templete that can be used for starting point?

No that's anything more than a demo AFAIK. If you have already written a
warehouse package in another language, you may already be aware of how to
set up the relations between the tables. There's a basic introduction in
this link:
Inventory Control - Quantity On Hand
at:
http://members.iinet.net.au/~allenbrowne/AppInventory.html

5. Is there migration software that convert my exsisting unix Inventory
system?

If you can export the data to ASCII, you can probably import it into Access.
You will not be able to convert the existing code.

6. If I setup my system on a windows base plateform would I be able to
set
up IIS so I can create a website that would show current inventory through
a
designated IP address?

It is possible to serve Access data onto a web page, using a technology such
as .Net, ASP, PHP, or Cold Fusion. Access has Data Access Pages, though it's
probably easier to use another approach if this is Internet based. The job
requires considerable work: you lose the great functionality of Access forms
and subform, and reports - the very things that make Access attractive to
start with.

 

[Rayrock]

How would I set up the front end? I would load the templates on the
machines and then link it to the database on the main machine, I.e host?

Is there an example?

Ray

 

[Allen Browne]

There are various ways to do this.

For the basics, see:
Split your MDB file into data and application
at:
http://members.iinet.net.au/~allenbrowne/ser-01.html

The best soluition is to consider the front end as the "application", and
install it to each user's workstation. If that's not practical, you can
actually place the front end in each user's private space on the server. If
the issue is keeping all the user's fe's up to date, see:
Auto FE Updater
at:
http://www.granite.ab.ca/access/autofe.htm

 

[rolaaus]

Allen Browne always supplies some great answers, but one thing I usually see
missed when discussing splitting databases for multiple users is a reference
to the Developers version of Access. It allows the creation of a "run-time"
version of the databse being created. Many the database, once developed can
be distributed to many users, who don't have MS Access on their system. The
reason I bring this us is because it can be more cost efficient to purchase
the Developers version of Access and install the run-time on everybody's
machine except the person creating the application. Even if you have 2 or 3
ppl developing the database, you can still purchase an Access license for
them, and have 1 developer version license and have that 1 license of
developer vers run the "distribution" process. I know this could possibly be
confusing, which is possibly why it is not referenced more often. Let me
know if you need further help, but you can probably find more info on MS
website by doing a searche for ODE (Office Developer Edition).