Re: Local tables vs. linked
- From: "aaron.kempf@xxxxxxxxx" <aaron.kempf@xxxxxxxxx>
- Date: 30 Nov 2006 18:17:42 -0800
ADP is a great solution; i really really reccomend it.
it is a lot simpler to troubleshoot
-Aaron
ciroteo wrote:
On 28 Nov, 23:11, "Mike" <nos...@xxxxxxxxx> wrote:
Hi,
I've an application connected to MSSQL. I need to create a table for the
local application which should not be part of the SQL but when I create it,
automatically it's created in the SQL server. How do I ensure that a table
stays with the application (not linked)?
TIA
--------------------------------------------------------------------------------
Estoy utilizando la versión gratuita de SPAMfighter para usuarios privados.
Ha eliminado 857 correos spam hasta la fecha.
Los abonados no tienen este mensaje en sus correos.
¡Pruebe SPAMfighter gratis ya!
for example you can create a table on the server, or by the way you can
use the same. Then You can add a field with autovalue the name of the
user or another uid. Then using a update query you can populate the
same table with all the record you need and a user value in the new
field.
In this way the user will update or manipulate only the records
matching his user name and
at the end of the procedure you will delete all the records you have
temporarly created.
hope it's clear!
.
- References:
- Re: Local tables vs. linked
- From: ciroteo
- Re: Local tables vs. linked
- Prev by Date: Re: How to hide Logon Lorm when open adp database
- Next by Date: linking Asp.net to sql server!
- Previous by thread: Re: Local tables vs. linked
- Next by thread: Re: Cannot Open SQL Server Table in Access.ADP File.
- Index(es):
Relevant Pages
|
Loading
