Inserting Views

Will the DB performance be affected by inserted views? And how about data-manipulation? Will the MS SQL Server (2005) automatically adjust/update the VSIFTs if I insert data manually through a sql-queries? Somebody told me to use the C/ODBC-driver instead but if I got it right it's just for the native database, right? Should I rather use "C/Front" to guarantee data-consitency? Best regards

What are you trying to do.

First of all I don't want to spend any money on developer license(s) or anything if it is not mandatory. So this is what I want trying to achieve: - I want to import reprocessed data into Excel 2007 like a usual SQL-Data-Source, that's what I need the Views for. Also the "send to..." function included in the Dynamics client is way to slow. I don't want to manipulate the Data in Excel, just read it refined. - I need to manipulate some data of products like their current location and (previous, current and next) operation numbers. Do I really need "C/Front" to do the second step or will some sql-query do the same job? Best regards

 Look into something like Jetreports.You will be able to view NAV data in excel. This will also work with flowfields.

I think there is no really need for Jetreports, since it is a SQL Database and I guess I can pull triggers as well as Jet-Reports can but for less than a few hundred or thousand $. I always need the same data reprocessed in the same way and Excel 2007 has SQL-Data-Sources integrated, so I'm just wondering about the database engine: will it be affected by inserted views or won't it even notice them. I mean are there like hash-values about the available tables/views validated by nav each time it runs or something?!