Picture advice/help

[yhgtbfk]

Hi guys.

I have been told to make my database look 'sexier' but I am a bit worried that the pictures may slow it down or increase it's size unneccesarily.

Speed is an issue because we have some offices that dial in and access it that way and as such are limited to their connection speed.

So what I want to do is created a few images, link to them, and put in code that can 'turn them on'.

The question is how?

I have created a new image object. Changed it's properties to linked.

Now I need some code that reads:

If myvalue = "Yes" then
myImage.visible = true
Else
'code to delete image
End If

I am a bit worried because that means that the images will always be there on load up, so loading the form will be just as slow because the images are there.

Or maybe I can do

If myvalue = "Yes" then
'code to create image
End If

Please help.

Edit - Part two to this question is: How do I use relative links for images? I have a folder of images and I want them to work no matter where the database sits.

Edit again - Just another question: Is it possible to have Images appear and disappear depending where the mouse is?

 

[Len Boorman]

"Sexier" is definately fattening with Access. and there will be a process overhead I think even if you try to control the image.

How about a sexy database for non dial up and a plain interface for the dial ups. Use linked tables for both and everybody is viewing the same data.

Re the links I think you will have to use absolute links and specify the path precisely and fully if you want them to work regardless of database location

L

 

[yhgtbfk]

Thanks for your help.

I am using the search function (as well as Google) as I type this, but I thought I would also ask you for advice:

Currently I have a database that is all in one. This is a problem because if there is a bug or enhancement, I have to change the entire database (which could potentially result in data loss).

I think linked tables will be a good idea, but I just want a few ideas:

1/ What is the best way to secure the tables so staff cant just access the table part?
2/ Is it better to have the data in a series of databases all linked to the one front end? Is this possible? What I mean is a database for vehicle bookings, and another for staff details, and the front end can interact with both.
3/ Are linked tables absolute or relative? Because this will be bundled onto a CD and sold.

Thank you.

 

[Len Boorman]

1/ What is the best way to secure the tables so staff cant just access the table part?
2/ Is it better to have the data in a series of databases all linked to the one front end? Is this possible? What I mean is a database for vehicle bookings, and another for staff details, and the front end can interact with both.
3/ Are linked tables absolute or relative? Because this will be bundled onto a CD and sold.

Thank you.

The approach I generally take is to have all tables in one database and then have an Interface or interfaces that use linked tables.

If the data is related then I would not have separate databases for say vehicle and staff. It could be done quite easily and interfaces could interact with both.

Linked tables may be absolute or relative. I generally use absolute since in my situation on a network people may have differing drive mappings.

I have no experience in the implications of selling applications so cannot really comment here.

Len