Importing to new database to handle security - SQL not importing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi there hope you can help,

I used the instructions at http://www.jmwild.com/security97.htm to secure my
database, I needed to do the manual routine due to having access 2000.
The problem I am experiencing is that when I import all of the information
from the original database as decribed - the SQL against the forms and
reports is not being carried with it,

How do I ensure that everything is imported accross - can anybody advise?

Thanks very much for any help

Kind Regards

Hazel
 
The problem I am experiencing is that when I import all of the information
from the original database as decribed - the SQL against the forms and
reports is not being carried with it,

If your forms' recordsources are SQL statements, those come with the forms
(I've never seen it not do this).

If your forms' recordsources are saved queries or tables, then you need to
import the queries. When you import, ensure you import *all* objects.
 
Hi Joan,

Sorry to confirm in more detail - its the SQL attached to events and command
buttons etc that dosent transfer along with the forms.

Is there a way to import this ?
 
huzzlepuzzle said:
Hi Joan,

Sorry to confirm in more detail - its the SQL attached to events and
command
buttons etc that dosent transfer along with the forms.

Is there a way to import this ?


I am not able to reproduce this at all. When you import a form, the code
imports with it. I don't know what to suggest.
 
huzzlepuzzle said:
Hi Joan,

Sorry to confirm in more detail - its the SQL attached to events and
command buttons etc that dosent transfer along with the forms.

Is there a way to import this ?

I agree with Joan. What you're seeing is not normal and I would venture to
say that what you describe is not really what is happening at all. When you
import a form you import the WHOLE form. There would not be an easy way to
import a form and leave the code behind even if a person wanted that
behavior.

Some piece of information is missing.
 
How do I ensure that everything is imported accross - can anybody advise?

You said Access2000 (thinks...flakey), and "import across" (thinks...good way
to find out).

I'd Decompile/Compile/Repair/Compact the original db (Backup!), then try
again. This will "clean" the database as far as possible.

(sledgehammer approach)

Chris

(not that this is related, but if importing you ARE looking at all the
"Options>>"?)
 
Say /exactly/ what you are doing, step by step, with particular
emphasis on which database(s) you open & how you open them. Like a list
of instructions for someone else to duplicate the problem, if they were
on your PC.

HTH,
TC
 
Back
Top