Darin,
your 'static' dataset is only read once - when an update is done. So, once
the user updates the application, you mdb is not going to accessed or used
again until the next update? Or is it read each time the user STARTS the
application ? I am a bit confussed here?
If the first ... read only once after the update ... why not use the xml
file approach. Speed will be an issue, but if it is a part of the update
process, the user can probably live with it - especially if there is a
noticable performance gain from utilizing the 64 bytes OS. However, if you
are pushing out updates every 4 hours, the user may become a little annoyed.
I would suggest that you test the 'speed' of loading an xml file specfic to
you needs. Many people over-use xml files and try to use them as a
'database' and expect the same results / speed they get from a database. Is
you Static database hugely relational or is it a few 'independant' tables
with a lot of rows in each? This will impact the speed of reading the xml
file.
If the second situation - read everytime the application is fired up, you
will have to either live with the deficiency with the Access OLEDB driver,
or you will need to test the loading of the XML and come up with a design
approach that offsets the performance / restrictions of running your
application in 100% 32-bit mode.
Jeff.
PS: I would suggest developing a process that utilizes sql db on the client
and issue a SQL file to be loaded with each update.
"Darin" <darin_nospam@n ospameverwrote in message
news:eK******** *****@TK2MSFTNG P06.phx.gbl...
My front-end is VB.NET, not access. The access MDB only contains all the
SQL text for views, stored procedures, etc.
I can look at an XML file, I haven't worked with any yet. I know from
reading the XML don't load real fast, but this file wouldn't be read all
the time, only when an update is done.
Darin
*** Sent via Developersdex http://www.developersdex.com ***
