If you rely on local storage of data, yet want to use ADP, try saving data as XML.
Example: the values of a combo box rarely change. Instead of hitting the SQL server each time, load the data once (on each DB load perhaps?) to local XML file, and retrieve that data into combo box using ADO. Gives you some MDB functionality plus more efficient server usage. HTH Bryant --- In [email protected], "George Oro" <[EMAIL PROTECTED]> wrote: > > I agreed on Tom... > > As per my experience, I dont suggest Access.mdb with SQL BackEnd but if you > really prefared using access as FE, use Access Project. But still it will > depends on the data traffic and your code technique. > > George > > > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] Behalf Of ivan > Sent: Tuesday, October 18, 2005 4:45 AM > To: [email protected] > Subject: [AccessDevelopers] Access as FrontEnd > > > as we know we can use many tools as FrontEnd such as > VB.Net,VB,Delphi,C#,Access,etc with SQL Server as BackEnd. > > My Question is : > > Do access have the same performance(speed) as FrontEnd compare to others > tools as front end, of course with the same BackEnd (SQL Server). Please > give me an explanation > > Thanks > > > > > > Please zip all files prior to uploading to Files section. > Yahoo! Groups Links > ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/q7folB/TM --------------------------------------------------------------------~-> Please zip all files prior to uploading to Files section. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AccessDevelopers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
