Popup Tables (1 Viewer)

[LadyMarmalade]

Greetings!
I'm making a few forms which appear as popups; various options here and there allow the user to view tables or queries (so, using VBA such as DoCmd.OpenQuery "Books on Loan", acViewNormal, acReadOnly)
However, these insistently appear as part of the access GUI as opposed to a seperate pop up. Is there any way I can solve this?
Thanks!
Lady Marmalade

 

[AlexHedley]

Hi

Which version of Access are you using?

Are they showing up as Tabs?

In File | Options | Current Database
Do you have your 'Document Window Options' set as Overlapping Windows or Tabs?

 

[namliam]

Strongly suggest you have a look at:
http://www.access-programmers.co.uk/forums/showthread.php?t=225837&highlight=naming+convention

 

[LadyMarmalade]

Strongly suggest you have a look at:
Insert URL here - stupid forum rules. - LM

Could you explain please?
I mean, the database/tables etc. itself are so ridiculously simple and unlikely to be edited that it doesn't make a huge difference there, but all my coding, button/object names etc. follows relatively easy to understand naming convention (e.g. button to display all books currently on loan is named viewOnLoan whereas button to display all available books is viewAvailable)

Don't know why I'm explaining that, XD, somewhat irrelevant.

Ugh won't even let me post. This is a seriously stupid rule.

Hi

Which version of Access are you using?

Are they showing up as Tabs?

In File | Options | Current Database
Do you have your 'Document Window Options' set as Overlapping Windows or Tabs?

Hmm...I thought it may be something like that :/
The issue is, when other people in the office use the database, my settings won't exactly carry over.
Given that this thing will be exported as a runtime program, can I have specific settings be carried over for the instance in which that program is active?

 

[AlexHedley]

@namliam it would have been handier to say what you thought the reason for posting that link was.

If you'd replied with a suggestion for an answer and also suggested best practices that would have been nicer.

@LM although it is a small database and your names are clear in what they do they aren't clear what they are, how do you know that's a query you're opening in your code? if you were to use the standard naming conventions it makes it easier for others to work out what your db does and if it were to expand you might not run into problems.
Get into the habit now and it'll help later.

Of course it's your db so if it makes sense to you then do it your way

The changes should be made to the db and not a user setting.

How are others using the db?
Is it on a network share that you can all access?
Is it a split db, tables in a backend db and forms, queries etc in a front end?
Have you sent a version to colleagues?

 

[LadyMarmalade]

@LM although it is a small database and your names are clear in what they do they aren't clear what they are, how do you know that's a query you're opening in your code? if you were to use the standard naming conventions it makes it easier for others to work out what your db does and if it were to expand you might not run into problems.
Get into the habit now and it'll help later.

Of course it's your db so if it makes sense to you then do it your way

Oh. Of course.
Thanks!

The changes should be made to the db and not a user setting.

How are others using the db?
Is it on a network share that you can all access?
Is it a split db, tables in a backend db and forms, queries etc in a front end?
Have you sent a version to colleagues?

The database will likely be on a network share which is accessible by all...I'm considering doing it via windows sharepoint.

It's not a split database - tables, forms, queries etc. are all in the same file (It'd be slightly pointless having a seperate database for the tables given that there are literally two tables?)

Nothing has been sent to colleagues yet. They barely even know I'm doing this :banghead:

 

[AlexHedley]

Ok, we'll check the db windows settings I suggested before and let me know.

If you're able to add a screen shot of what is happening that might help diagnose it better too.

 

[namliam]

Well read the link...
It is good practice to prefix it all and NOT use spaces in names.
I.e.
instead of a query "Books on loan" use "qryBooksOnLoan"
instead of a button "ViewOnLoan" use "btnViewOnLoan"
Etc etc... Then again its only friendly advice, feel free to ignore it

 

[LadyMarmalade]

Ok, we'll check the db windows settings I suggested before and let me know.

If you're able to add a screen shot of what is happening that might help diagnose it better too.

Right! It does open in new windows now, but it opens in the background (behind the current form).
Any way to deal with that?
Thanks!

P.S. I can add a screenshot via zipped file, but I don't see how that'd help...

 

[AlexHedley]

Try 'Modal' and 'Popup' depending on your needs


@namliam it's great advice from you and agree with it 100%, your latest reply would have been a more constructive one than just read a link.