MS access data processing

[babyjames081109]

---

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 stand-alone application na yan (correct me if im wrong)

yes bro tama! ganito kasi, yung mga developer namin nag try ng centralized pero ang gamit nila eh client pc lang at mabagal daw kaya solution nila stand-alone na lang.. eh mejo opportunista ako kaya sabi ko itry muna using our main server at kung talagang mabagal eh upgrade tayo ng RAM.. may point naman ako diba.. hehe

[babyjames081109]

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 stand-alone application na yan (correct me if im wrong)

yes bro tama! ganito kasi, yung mga developer namin nag try ng centralized pero ang gamit nila eh client pc lang at mabagal daw kaya solution nila stand-alone na lang.. eh mejo opportunista ako kaya sabi ko itry muna using our main server at kung talagang mabagal eh upgrade tayo ng RAM.. may point naman ako diba.. hehe

[tsunade]

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

yep sakto bro..

[babyjames081109]

okay bro thanks! ewan ko lang kung iconsider nila.. hehe..

[slkmclaren]

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!

MS Access does not need a Server to reside on. Just boost the MEMORY (RAM) of the computer where the database resides and also the client computers. You may also have to check your network equipments like network cards, cabling, hubs and switches. Newer network cards with 1000 MBits peforms better than older ones with 10 or 100 MBits. Switches transfers data faster than hubs.

Kung mag-LAG ang inyong mga client computers its because basin naay problema sa coding. Especially macro man diay ang gigamit ana. Try to check what engine is used in data access. For improved data access performance consider using DAO not the native MS JET engine. You shouldn't have a problem fetching a single record for display and editing purposes.

Ang 20K nga entries is gamay ra na para mag-LAG ang data access. Cguro kung naay bottleneck is kung mag-dungan mo generate mo ug report which is unlikely.

[Cometburn]

i agree with tsunade. Separate mo yung gui at backend. mas mabilis ng konti pero kung kaya nyo i rewrite yung program, ganun nalang gawin nyo. gamit kayo ng centralized db gaya ng mysql or ms sql. Tanggal yang sakit sa ulo nyo. Yang access kasi may panahon na mapupuno yan. Wag nyo na isa-isahin paglalagay sa client nung program mas masakit sa ulo yan kapag may report na hahanapin.

[garlic]

based on experience, naay limit ang access. mabuang na cya kung dghan na kaau data. naa mi client nga g revamp namo ang system from access ky nka buang2x ang data tungod sa kadako. it was costly but better among ghimo ky more innovative and cloud based.