MS access data processing

[babyjames081109]

---

mga expert pa help lang... here's the situation..

we have a program made in ms access, our daily transaction is about 20k entries...
anong specs po ng server ang pwede magamit para hindi ma lag yung transaction namin pag nagsasabay sabay yung 15 users (or 15 pc) sa pag access sa database...

thanks!

[anonymousprogrammer2012]

access? LOL...

[babyjames081109]

haha... 2010 naman to bro..

[tsunade]

postgreSQL bro or MySQL its all free. you can still use ur front end just split it and convert ur data to pSQL or mySQL, make sure you back-up ur data before converting and splitting. sagdi na lang ng mga stereotype. kataw-an lang ang access. ^^V

[babyjames081109]

postgreSQL bro or MySQL its all free. you can still use ur front end just split it and convert ur data to pSQL or mySQL, make sure you back-up ur data before converting and splitting. sagdi na lang ng mga stereotype. kataw-an lang ang access. ^^V

the sad thing is mga katrabaho ko lang yung nagdevelop sa access using macro programming yata i'm not sure.. same codings lang ba yun sa mySQL?

[sLY26]

TS, i assume nga local network ra ni nga application. unsa man diay ang specs sa imong current server?

[babyjames081109]

intel xeon (not sure sa exact details), 4 gb ram, windows server 2003... my co workers tried it on LAN using basic dual core pc with 2 gb ram kaya ang solution nila i distribute nalang yung program per pc, meaning per pc din yung database..

[tsunade]

the sad thing is mga katrabaho ko lang yung nagdevelop sa access using macro programming yata i'm not sure.. same codings lang ba yun sa mySQL?

NOPE indi pareho bro.. split mo lang yung msaccess mo to Front-end and Back-end, where backends contains the data & the front end contains the GUI.. convert mo yung backend to mysqp or psql... after that, setup mo sa front end mo, locate mo yung converted database server mo. IT na nyo ang bahala sa convertion kung meron. ^^

sorry taka lang kog tagalog..lol ^^V

put-up some more RAM bro cuz database are RAM monsters

[babyjames081109]

NOPE indi pareho bro.. split mo lang yung msaccess mo to Front-end and Back-end, where backends contains the data & the front end contains the GUI.. convert mo yung backend to mysqp or psql... after that, setup mo sa front end mo, locate mo yung converted database server mo. IT na nyo ang bahala sa convertion kung meron. ^^

sorry taka lang kog tagalog..lol ^^V

put-up some more RAM bro cuz database are RAM monsters

hehe.. thanks bro.. meaning pwede pa rin magamit yung access as front-end then SQL as back-end? correct me if i'm wrong...

[sLY26]

intel xeon (not sure sa exact details), 4 gb ram, windows server 2003... my co workers tried it on LAN using basic dual core pc with 2 gb ram kaya ang solution nila i distribute nalang yung program per pc, meaning per pc din yung database..

medyo okay lang yung specs ng server TS for 15 clients, medyo naguguluhan lang ako, di ba kailangan na centralized yung db ng application na yan? wherein yung db naka reside sa server. kung each of the pc may separate db, meaning parang stand-alone application na yan (correct me if im wrong)