File Permissions and Speed

[cregy]

Hi

I am totally new to access and I am actually a network engineer with no clue as to how to move forward!

I am running a network for a company that uses Sage as an accounting programme. It also uses a plugin to export the tables to .csv for importing into access for reports and other work to be done.

These tables tend to be rather large and are slow. We are also constantly getting file permission issues and write to tables problem. I am cursed(!) with trying to speed things up and also sort out the network issues.

I have been reading up and one of the ways of speeding things up is putting the tables on the network for all to access and separating the front-end and placing these on all users. Does anyone know of an easy to understand tutorial on doing this please?

The tables are currently stored on a Mac pro and accessed by xp boxes. Will this cause problems please?

I know I have a ton of questions but can't think of them at the moment. I'll add them as I can. Thanks for all the help.

Rich

 

[NigelShaw]

Hi,

its definately a permissions issue though im not entirely familiar with OSx. if you are sharing a file from a mac to windows, doesnt the user have to be added to a keychain in the mac os security?

i do kno that the security structures are different between windows and mac. i have a pc and my wife has a mac, were both in the same workgroup and yet cannot share files!!

why cant you just save the database files on the server?

Nidge

 

[Banana]

Pretty sure it should be doable.

You, of course, have to configure the computers to allow sharing.

Maybe it'll give a clue.

Nigel is right, though, you would find much easier to use a server or at least a NAS to share the files.

 

[gemma-the-husky]

i may be wrong here

sage output csv's are not likely to be normalized for access

working directly with csv's is not likely to be very efficient. one idea would be to import them into access, and find a way of adding them to normalised tables in your database - the problem here is/might be generally distinguishing between new lines on the csv, and changes in existing lines.

--------
in terms of splitting databases, in a multi-user environment the accepted methodology is to have

a) the data files in a central location
b) the forms/queries etc in a separate database, with each user having his own copy. Note that this may mean licensing more access copies.

99% of things work in a transparent manner - a few things dont work in a split environment

achieving this split is a 5-minute task. There is a wizard, but once you see what its doing, its a simple task to do it yourself.

---------
is it sage 50?

an alternative to getting the csv off sage, and importing it, is merely to connect to the tables directly in Sage - they are likely to be pretty well normalised anyway.You could always make copies of these Sage tables in your database, if you want to avoid the risk of writing to the Sage tables

you can probably do the same with Sage 100 and other products, but I am not familiar with the other versions.